- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Jan 2022 17:43:05 +0000
- To: public-css-archive@w3.org
> The reason why is the need for the UA-manipulated stuff to be on top. I don't have an objection to considering exposing another top layer to developers that is below the UA one, if there is a strong use case, so long as it doesn't get in the way of the UA one. By arranging it this way, aren't there going to be odd situations? What happens if a fullscreen element or modal dialog puts something into the "developer top layer". It'll be below the fullscreen/dialog and never visible. For example, what if you want a tooltip on top of a modal dialog? That would be impossible, or would require special case logic to do something entirely different if your dialog was modal. On the other hand, if the **one** top layer was managed by the UA, it could allow nested top layer elements like this, with more specific rules. For example, it's ok to show a tooltip on top of a popup on top of a fullscreen element, but if the user hits ESC, **the entire stack of three elements** gets removed from the top layer. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6965#issuecomment-1021446826 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 January 2022 17:43:06 UTC