Skip to content

[CSS2] define and use a term for things that create a stacking context #3102

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

Open
dbaron opened this issue Sep 12, 2018 · 2 comments
Open

[CSS2] define and use a term for things that create a stacking context #3102

dbaron opened this issue Sep 12, 2018 · 2 comments

Comments

@dbaron
Copy link
Member

dbaron commented Sep 12, 2018

This is a subtask of #2717 covering only the edits to CSS2, and not the edits that will be needed to other specs to depend on the edits to CSS2.

Per working group discussion today, we want to add a term to CSS2 for things that create a stacking context. We then want to rewrite relevant parts of the spec (for example, some but probably not all of the references to "positioned descendants" in Appendix E) to use this term, so that when other CSS specs add to the term, they will be referenced appropriately.

Some of these edits require some care. For example, bullet point 8 of Appendix E currently begins:

All positioned descendants with 'z-index: auto' or 'z-index: 0'

and this is interesting because:

  • of these conditions, having z-index: 0 (when z-index applies, i.e., when positioned) establishes a stacking context but z-index: auto does not
  • z-index only applies to things that are actually positioned, and not to the other things that establish a stacking context
  • everything else that establishes a stacking context should be considered here, unless it's also positioned and has a z-index other than auto or 0 which moves it to bullet point 3 or 9.

so the revised wording needs to account for all of this.

I suspect an appropriate place for the definition may be in 9. Layered presentation (maybe or maybe not in the existing 9.9.1 subsection). I suspect that section will also require edits. Some other sections may as well.

@fantasai
Copy link
Collaborator

@smfr suggested “stacking contextainer” as a joke on the call, but “stacking container” seems pretty reasonable.

@SelenIT
Copy link
Collaborator

SelenIT commented Sep 16, 2018

Maybe something like "stacking root" would also work, similarly to the "flow root"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants