Jen Simmons
Jen Simmons
To be clear — both in response to @ahmadalfy's comment, and to some reactions I saw on Twitter: no one is proposing that the CSSWG put all the separate specifications...
According to [this blog post](https://adrianroselli.com/2022/07/its-mid-2022-and-browsers-mostly-safari-still-break-accessibility-via-display-properties.html), ``, ``, `` are not accessible when `display: contents` is applied in Chromium 103 on Windows 11 or Android 12. I expect that's still true...
Could you please add a description and update the title for this PR, so it's clear what this is about?
For example, recently iOS 15 updated to iOS 15.7, while the version of Safari updated to 15.6.1.
Please do create new images for your tests. The specs for AVIF changed since the early days. Image encoders have been updated — including in Sept 2022, when AVIF bugs...
Once again, I have an error in the new file I'm trying to create. I often don't know how to handle the formatting of notes/bugs/resources when those fields are empty....
Thanks @Fyrd! This file passes, keywords and all.
I just asked our engineers if there's a demo from FIDO Alliance that could serve as a great test, but it seems like not. They did clarify that supporting passkeys...
I would love to see this. I would also recommend thinking carefully about the wording of the banner, so it conveys something that means "hey, this isn't in every browser...
I'm not sure that Style Queries for standard properties will ever happen. It's likely it will not.