Re: [csswg-drafts] anything that creates a stacking context should sort in the positioned descendants z-ordering list

The CSS Working Group just discussed `anything that creates a stacking context should sort in the positioned descendants z-ordering list`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: anything that creates a stacking context should sort in the positioned descendants z-ordering list<br>
&lt;tantek> lol "perfectly fine HTML elements". ok agree to disagree<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2717#issuecomment-416803673<br>
&lt;dael> florian: I ran into this again while writing tests for Contain. Summary: place in the spec that defines how things stack is in css2.1 THat bit of prose assumes only things that can create stackign context are positioned elements so it's not careful in phrasing. We've introduced other things so we need to clarify if they stack same or not.<br>
&lt;dael> astearns: Stacking or painting?<br>
&lt;dael> florian: I'm not the expert on stacking and painting. I jsut want this closed.<br>
&lt;dael> dbaron: I think most of answer in the issue. Someone needs to propose edits to css2 with a new term, only onething in css2 uses the term, all other specs use that term.<br>
&lt;dael> chrisl: Not just css2. Also compositing defines more. I agree we need clarity and changes, but all in css2 is not optimum.<br>
&lt;dael> dbaron: Things that should be in compositing, I agree. Term in css2 is 'thing that creates stacking context'. When css 2 refers to that term it says 'positioned elements' and it needs a term so other specs can say this thing creates stacking context so all things css2 says about stacking context applies<br>
&lt;dael> chrisl: agree on that<br>
&lt;dael> florian: Given css2 has editors can we assign somebody?<br>
&lt;dael> tantek: File and issue and take it from there<br>
&lt;Rossen_> :)<br>
&lt;dael> fantasai: gsnedders is still looking for funding to work on css2 so if you want him to be an effective editor give him some money<br>
&lt;dael> astearns: I like idea of separate issue for css2 work o nthis<br>
&lt;dael> florian: Is it separate or just the same?<br>
&lt;dael> tantek: Yes<br>
&lt;dael> dbaron: Edit other specs. Separate issue makes sense<br>
&lt;dael> tantek: Fixing css2 is not signing up for all other specs<br>
&lt;dael> dbaron: And fixing css2 is complicated because you have to find all the places to change for the new term<br>
&lt;dael> astearns: tantek can you create issue?<br>
&lt;dael> tantek: Not failiar. I'd ask current issue creator<br>
&lt;dael> dbaron: I'll file and issue<br>
&lt;dael> astearns: Anything more?<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2717#issuecomment-420709643 using your GitHub account

Received on Wednesday, 12 September 2018 16:19:25 UTC