Luke Warlow

If we go on the basis that this would utiltise the `invokerbutton` proposals. I guess the question is what would the action be and would we need any additional attributes...

I agree that using the content-visibility: hidden and hidden until-found mechanism (probably implicitly like details does) is probably better than toggling display. I guess it does beg the question is...

> Yikes! I think I got confused because a lot of the documentation3 about hidden=until-found4 it mentions the fact that content-visibility: hidden is used instead of display: none right along...

Adding to agenda to discuss in more detail and try and get the ball rolling because this feels like a useful addition and something we should be able to gain...

https://github.com/openui/open-ui/issues/863#issuecomment-1760226526 could it be due to the property limitations mentioned here? Or I guess if it's not using the pseudo element potentially not?

Hmm that's an interesting idea. Could apply the default hide this from accessibility tree behaviour. Would it require an SVG / img (well I guess anything) child or if you...

I think the intention was to remove the marker pseudo but not to remove the default marker right? So the default UI would still look like currently?

I can't think of how this is introducing any new attack vectors* off the top of my head? Having said that it's definitely something that'd be good to get more...

https://demo.lukewarlow.dev/fullscreen/ - These two iframes demonstrate a potential new security risk of the fullscreen actions within a sandboxed iframe. Currently fullscreen API requires javascript so a sandbox without "allow-scripts" won't...

"Would these attributes be subject to CSP, sandboxing or specific HTML sanitizer behaviour at all?" - a question raised in the Mozilla I2P.