-
Notifications
You must be signed in to change notification settings - Fork 22.6k
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
Move specificity and cascade under CSS cascade module #38125
Conversation
Preview URLs (63 pages)
Flaws (158)Note! 40 documents with no flaws that don't need to be listed. 🎉 URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
External URLs (1)URL:
(comment last updated: 2025-02-12 23:01:32) |
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.
r=me for mdn/content-mathml
This pull request has merge conflicts that must be resolved before it can be merged. |
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.
This restructuring makes sense, and I think the changes look good. I just have an overarching concern with your choice of slug for the "Introducing the CSS Cascade" article.
/en-US/docs/Web/CSS/CSS_cascade/Cascade
is a bit weird and confusing, and doesn't helpfully describe the article's purpose. I think /en-US/docs/Web/CSS/CSS_cascade/Introduction
or /en-US/docs/Web/CSS/CSS_cascade/Introducing
would be better. WDYT?
These PRs are just to move content; I kept the original slug, just adding the directory. |
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.
OK, approving. We can always improve the slug at a later date.
specificity is defined in CSS cascade and inheritance