- From: SelenIT via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 May 2018 07:33:53 +0000
- To: public-css-archive@w3.org
> it has no box, it's descendants could be anywhere in the layout tree. It seems like a really weird behavior to explain to any user IMO... Completely agree that it's weird. Exactly like the focus behavior of, e.g., an off-screen positioned element with on-screen absolutely positioned children, or the focus behavior of the element with good old `outline:none` and no replacement for it. Sure, it is bad. But, just like in case of `outline:none`, it can be fixed by applying special styles to the element's descendants. Sure, this possibility (as many others in CSS) can have bad effect on the usability, and the spec probably should warn against misusing/overusing it. But removing the element from the accessibility tree altogether _without any_ possibility to restore its _displayed_ parts back and return the focus behavior to the less surprising state, as browsers currently seem to do, looks _way_ more problematic to me, regardless how good the intent of this behavior was. -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2632#issuecomment-385889662 using your GitHub account
Received on Wednesday, 2 May 2018 07:33:56 UTC