Re: [w3ctag/design-reviews] WG Revision: CSS Anchor Positioning Level 1 (Issue #1182)

lukewarlow left a comment (w3ctag/design-reviews#1182)

Hi, TAG has discussed this and overall this looks good but we have some specific concerns around the `position-visibility` property.

Firstly, there's concerns that this property doesn't actually address common developer needs. Trying a simple
[demo](https://codepen.io/lukewarlow/pen/XJNWQjg) where you have a sticky header and the invoker button
scrolls underneath the sticky header, the expected behaviour doesn't kick in.

We also have questions around the accessibility side of this property, when the anchor positioned element (in the above case
a popover) is hidden, the specification seems to show that it should be hidden from the accessibility tree. There's
concern about what happens when your focus is inside the popover when it's hidden. It would be good to have
further explanation on what is expected here.

Then there's questions specifically around the iteraction with popovers, when they're hidden they still match `:popover-open`,
in the accessibility tree they (presumably, see above) are hidden but their button presumably keeps it's aria-expanded state? There's also no toggle events fired when the popover hides or shows. Again it would be good to have further explanation on what is expected
and why that's the correct behaviour.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1182#issuecomment-4923843108
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1182/4923843108@github.com>