Re: [whatwg/fullscreen] Consider removing the containing block adjustment for popovers (Issue #218) from Mason Freed on 2023-03-14 (public-webapps-github@w3.org from March 2023)

From: Mason Freed <notifications@github.com>
Date: Mon, 13 Mar 2023 17:59:16 -0700
To: whatwg/fullscreen <fullscreen@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fullscreen/issues/218/1467184653@github.com>

Hmm, I really think popover top layer behavior (including this containing block adjustment) should follow the other top layer things like dialog and fullscreen. This is a key use case for popover, actually: one of the big hassles with userland popovers is that the popover usually has to be parented to some element placed at the end of the `<body>`, to avoid containing block problems like ancestor clipping or transforms. The top layer nicely solves that, allowing popover content to be DOM-located next to the invoker and the rest of the content, which is convenient, but also good for a11y.

This is precisely what the [anchor positioning API](https://developer.chrome.com/blog/tether-elements-to-each-other-with-css-anchor-positioning/) is built to solve. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/issues/218#issuecomment-1467184653
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fullscreen/issues/218/1467184653@github.com>

Received on Tuesday, 14 March 2023 00:59:28 UTC