- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Nov 2024 21:48:14 +0000
- To: public-css-archive@w3.org
So given the more recent discussions in https://github.com/whatwg/html/pull/9425 and https://github.com/mozilla/standards-positions/issues/772 and elsewhere, I'm coming back to this issue. I think the idea of propagating the outline to children (possibly recursively) mostly makes sense, although it may or may not be quite difficult to implement. I think there are a few issues we'd need to sort out at a conceptual level, though: * Is it a "merged" outline or separate rectangles around each child? (Chrome does "merged" outlines for multiple lines of links, and I think this sort of merging was part of the original intent of `outline`. I'm not sure about the current state in other browsers.) * How do we handle children that are text nodes? Text nodes normally don't draw outlines. If we do a "merged" outline I think we could associate it with the first relevant child (for z-ordering, filtering, etc. purposes). Or maybe the last one if outlines aren't (in some engines, at least) implemented at a special position in the z-order. I think the difficult parts from an implementation perspective probably relate to getting invalidation right when things change (such as changes to the size of the children or addition or removal of children). -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3323#issuecomment-2494920064 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 22 November 2024 21:48:15 UTC