-
Notifications
You must be signed in to change notification settings - Fork 25.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: remove unused CSS rules #40069
Conversation
Removed rules don't affect their component views. The reason - the templates don't contain elements to which that rules are applied. See https://angular.io/guide/view-encapsulation for more details
8155329
to
958fbc4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Thx, @AlexElin 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed-for: global-docs-approvers
Removed rules don't affect their component views. The reason - the templates don't contain elements to which that rules are applied. See https://angular.io/guide/view-encapsulation for more details PR Close #40069
Removed rules don't affect their component views. The reason - the templates don't contain elements to which that rules are applied. See https://angular.io/guide/view-encapsulation for more details PR Close angular#40069
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Removed rules don't affect their component views because the templates don't contain elements to which that rules are applied.
See https://angular.io/guide/view-encapsulation for more details
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information