Styling precedence

[kannanwisen]

Describe the problem that you experienced

I think, the explanation under Styling precedence Heading is inappropriate.

Enter the URL of the topic with the problem

https://angular.io/guide/class-binding#styling-precedence

Describe what you were looking for in the documentation

No response

Describe the actions that led you to experience the problem

No response

Describe what you want to experience that would fix the problem

No response

Add a screenshot if that helps illustrate the problem

No response

If this problem caused an exception or error, please paste it here

No response

If the problem is browser-specific, please specify the device, OS, browser, and version

No response

Provide any additional information here in as much as detail as you can

No response

[alan-agius4]

It does look like there is a page for this which is not linked from anywhere.

https://angular.io/guide/style-precedence

[kannanwisen]

It does look like there is a page for this which is not linked from anywhere.

https://angular.io/guide/style-precedence

Yes, even saw that. Under styling-precedence heading the content is irrelevant. This link has to be provided https://angular.io/guide/style-precedence.

[bob-watson]

@kannanwisen Thanks for the feedback, but I'm not sure what you mean by irrelevant.

Do you mean to say that the content below the Styling precedence heading is not helpful (which is what it appears to be to me)?

Would linking to Style Precedence, or perhaps replacing in Class and style binding with the info from Style Precedence be more helpful?

[kannanwisen]

@kannanwisen Thanks for the feedback, but I'm not sure what you mean by irrelevant.

Do you mean to say that the content below the Styling precedence heading is not helpful (which is what it appears to be to me)?

Yes, it is not helpful.

Would linking to Style Precedence, or perhaps replacing in Class and style binding with the info from Style Precedence be more helpful?

I feel the below link is better

Replacing in Class and style binding with the info from Style Precedence be more helpful?

[avmaxim]

@kannanwisen @alan-agius4 @bob-watson From my point of view - we have to keep the docs aligned with the DRY principle where possible, so I encourage avoiding docs duplication in two places: Class and style binding and Style Precedence. Even more, I suggest removing this section - ## Style Precendece - from Class and style binding because we already have references to Style Precedence docs in the following sections - ## Binding to multiple styles and ## Binding to multiple CSS classes. I added a bit more info to them to make it more transparent. It will also avoid extra code duplicates and confusion among developers.

I prepared a PR for your review. Feel free to add any comments:

• docs(docs-infra): improve docs for styling precedence and class binding. #49435

[JamesHenry]

FYI the guide has not been migrated to angular.dev at all, I opened this one to track that: #56085