- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Jan 2022 14:41:22 +0000
- To: public-css-archive@w3.org
> Isn't it just the fact that you can have one but not both? That is, you either control access via CSS but can't select, or you can select but then you can't control access via CSS. I don't know what "other reasons" are though, so the choice of whether to allow selection or access is probably decided by something else The basic issue is that the UA controls the top layer, and can “kick out” elements. E.g. both full screen elements and modal dialogs get forcibly removed from the top layer when you hit ESC. If access to the top layer were provided by CSS (say via a `position:top-layer` property), what would happen in this case? Would `computedStyle` still say `position:too-layer`? Worse, how would one re-request top layer access in this case? By removing the property and re-adding it? The issue is that CSS can’t really be modified by the UA. But if top layer access was provided by something like `<div toplayer>`, then the UA could just remove the attribute when needed. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6965#issuecomment-1017578477 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 January 2022 14:41:24 UTC