- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Apr 2023 00:27:55 +0000
- To: public-css-archive@w3.org
> It was discussed in a CSSWG calll, see https://github.com/w3c/csswg-drafts/issues/8189#issuecomment-1479815485. From the notes, the model wasn't really covered in detail. > Yes, as far as I can tell I or Chris answered all the questions you raised, @nt1m (in https://github.com/w3c/csswg-drafts/issues/8189#issuecomment-1492399214 and https://github.com/w3c/csswg-drafts/issues/8189#issuecomment-1507524156), and you didn't respond any further . If we skipped something, please restate, with our apologies. Ah I missed the last comment of #8189, sorry. I did ask for a new issue to be filed, since it takes time to review specs on our side in general, and having a proper place to do it without things fall in the void is generally good. Anyway, I guess we can re-use this issue. > unless you explicitly ask for immediate removal, removal instead just adds it to the pending removal list, and it's removed for real during HTML's Update The Rendering. This ensures that transitions added at the same time will get processed and can have an effect on the 'overlay' property, possibly delaying the actual removal. (Immediate removal should only be used for security-related things, or when CSS isn't relevant, like if the element has been removed from the document.) This doesn't quite explain how this works relative to transitions, afaik, removing from the top layer kills the transition, so this means update the rendering will kill all pending removal transitions for overlay at least, so this makes me question whether this model actually works. This is the main part I wanted clarification about. In general the spec could use more precision around the role the `overlay` property actually plays in top layer rendering. That would also help understanding things around transition timing as well. From reading the spec right now, adding to the top layer will trigger right away "rendered in the top layer" style adjustments, so this makes me question what the `overlay` property is useful for. > User agents may, at their discretion, remove a running transition on [overlay](https://w3c.github.io/csswg-drafts/css-position-4/#propdef-overlay). The conditions for this are intentionally undefined. (This is to prevent potential abuse scenarios where a [transition: overlay 1e9s;](https://w3c.github.io/csswg-drafts/css-transitions-1/#propdef-transition) or similar attempts to keep an element in the [top layer](https://w3c.github.io/csswg-drafts/css-position-4/#document-top-layer) permanently.) I do think this should be defined, it is quite an important part of the feature design. -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8730#issuecomment-1526810713 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 April 2023 00:27:57 UTC