Rewrite of CSS/Building Blocks/Cascade and inheritance #6899
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SebastienWae
requested review from
a team and
rachelandrew
and removed request for
a team
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is related to #6384.
IMO the current article is confusing. Some of the terms used differ from the CSS specs, and inheritance can be introduced separately after the cascade.
My goal is to reorganize the articles and make the content more in line with the specs.
This is a first draft to get some early feedbacks, since it's my first proper try at writing technical documentation.
I'm also wondering if it would be better to put the selector articles before the cascade.
CONTENT:
TODO: