- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Jan 2022 19:41:37 +0000
- To: public-css-archive@w3.org
> Well, yes and no. Today, if you have a fullscreen or modal dialog, you have to know that, and put your tooltip as the last child of the fullscreen or dialog element rather than the body, in order for it to show up on top. So it's a problem today. But I'd hate to make it worse by ushering in a whole new capability that was rife with the same problems. I would hope we could make this easier for developers by just having one top layer which behaves rationally. And in most normal situations, things "just work". In the corner case (e.g. user hits ESC), the UA has the power to pull things back out, but developers don't have to worry about that at all. > > Maybe I'm overthinking this. But some use cases sound common. A tooltip on a dialog sounds familiar. A pop-up volume slider on a fullscreen video sounds familiar. I'd just prefer to have a solution that covers these use cases and doesn't make them harder than they are today. In these cases, if the author tries to use the CSS top level to put something on top of a UA-top level element, they'll fail *immediately* and see what's wrong. And it fails in the exact same way as "put it as the final body child" does. In either case, the author will realize their error the *moment* they test it, and then switch to the appropriate technique (last child of the dialog or whatever). I still don't understand why this is an argument against making "put it as the final body child" easier and more convenient for authors. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6965#issuecomment-1024574371 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 January 2022 19:41:38 UTC