- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Jun 2018 19:15:56 +0000
- To: public-css-archive@w3.org
Functionally, _the element subtree_ is clearly the part of the element: it passes the events to the element, it inherits the CSS properties where possible, and it triggers the element's activation behavior. The only thing that `display: contents` changes (to _literally nothing_) is _just one box_ in the box tree, the box of the element itself. But for the user, there is no difference between "clicking the button" and "clicking the button contents", as long as they result in the same action. _This_ is already the case in current implementations. And it should be, because > the `display` property only affects visual layout and not the interactivity of _the element_ and its descendants (with the _one and only_ exception for the `none` value). In my opinion, we should find the way to preserve the states of the boxless active elements that the user can interact with trough their subtree. Although _technically_ it's a new problem for CSS, _functionally_ it reminds me much of the case of visible labels for off-screen controls I mentioned before. -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2632#issuecomment-393982782 using your GitHub account
Received on Friday, 1 June 2018 19:16:00 UTC