rem on Nostr: npub1zylk3…ct54n I was forwarded your article on display: contents ...

npub1zylk3x2cvl79r854gtnqjvh7cjns6zzynvf39llvfvh6gl89cgvslct54n (npub1zyl…t54n) I was forwarded your article on display: contents (https://adrianroselli.com/2018/05/display-contents-is-not-a-css-reset.html) and I _think_(?) maybe Chrome and FF have resolved the issue of nested elements now appearing in the a11y tree (but this is a TIL for me, so I'm wary I could likely be wrong).

This link element is wrapped in a web component that has display: contents but link appears in a11y tree.

/cc npub1qwkaun0pqpnzswj2c0gtn2aggllvxwzvt855qnft7vw3zcc5dh2sjh8gvk (npub1qwk…8gvk) (because I feel like you might know for sure too…)