- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Jul 2018 23:20:07 +0000
- To: public-css-archive@w3.org
@SebastianZ I'd imagine there's nothing wrong with handling it the same way we already handle multiple elements with the same `z-index` values in the same stacking context, we let the document order be the last defense? These keywords could at least be *some control over a need to put one element in front or behind everything. As far as the ads example, people can always choose to run "broken" ads if they want, at least the ad might thrash the users experience a bit less this way? Though I understand @tabatkins reservations in people misusing this, like is often already done with `z-index`, it would be nice to have a way to more easily find the front or back of a stacking context. Even if we never get this in css land, it could be nice to have an api for a documents stacking contexts and their non-auto participating elements, without having to run gCS up and down. -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2444#issuecomment-401966094 using your GitHub account
Received on Monday, 2 July 2018 23:20:11 UTC