Jen Simmons

It seems that browsers are going through 4 stages of support for accessible content and `display: contents`: A) No support. `display: contents` is not recognized. B) Partial support. `display: contents`...

Firefox went from Stage B to Stage C with FF52. These are the current tickets for remaining bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=1500958 https://bugzilla.mozilla.org/show_bug.cgi?id=1553549 Here's a Chrome ticket: https://bugs.chromium.org/p/chromium/issues/detail?id=835455

I believe this PR can be closed as out of date. All browsers now have full support for `display: contents`. (See other recent PR for info about Safari 16 fixing...

@mirisuzanne You might be interested in weighing in here.

I definitely agree we should keep pages like this around for reference. I do not want to delete it. I disagree that web developers should consider using Regions for older...

I can only reproduce this inside the CodePen interface. Did you experience this bug in CodePen "debug" mode, or on a page that's not connected to CodePen?

It would also be very helpful if you could file this as an issue at https://bugs.webkit.org. Thanks!

>Safari 15.4 claims to support lazy loading, it barely does This is not accurate. Safari 15.4+ does support lazy loading, and it works very well. It seems there is a...

This bug is fixed in Safari 16 beta.

re: [Chris' comment](https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-585308306) above: I believe the Snapshots and this should be two different things. The Snapshots are heavily dependent on the CSSWG process, and where exactly in the process...