Update Chromium data for CSS visibility: collapse#26613
Conversation
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
There was a problem hiding this comment.
Thank you, this goes in the right direction.
- I added two review comments below.
- To update the Opera and Opera Android data:
- Opera 49 corresponds to Chrome 62.
- Opera 78 corresponds to Chrome 92
- Opera Android 46 corresponds to Chrome 63 (and Chrome 62 was skipped)
- Opera Android 65 corresponds to Chrome 92.
PS: Ideally, we should extract a subfeature table_elements (see this comment), and consider browsers treating visibility: collapse like hidden as partial_implementation (adding a separate support statement if they used to do this, but meanwhile fully support), but we can keep the scope of this PR small by updating/improving the notes, as long as we're consistent across browsers.
Edit: Another subfeature for ruby_annotations pointing to this spec would make sense.
Awesome thanks! I think you mean Opera Android 46 corresponds to Chrome 63 correct? |
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
|
I'm trying to figure out how to word this so we properly convey what is and what is not supported. From the MDN page, I see: Based on this information, we know |
|
@joswhite Thank you. For now, could we keep the notes verbose to avoid ambiguity? That last note may not be 100% accurate (regarding flex items), but I think it will be easier to fix that way. PS: As for Ruby annotations, I just tested this example from the CSS Ruby Annotation spec in Chrome 135, and Ruby example
|
|
Sounds good! I've updated the notes for Edge, Chrome, Opera, and Opera Android. Does this look good? |
|
This pull request has merge conflicts that must be resolved before it can be merged. |
…p>` elements before Chrome 92 (and corresponding versions of like browsers).
|
I just updated the PR to clarify that |
visibility: collapse;
visibility: collapse;visibility: collapse
|
Great thanks!! |

Summary
As described in #24185, Chrome compatibility data for
visibility: collapse;needs to be updated. Previously, it did not work properly for several table elements, now it does.Note: we should consider also updating this for other browsers, including Edge, which will need a note that in Edge 79-91 it exhibited the same issues as Chrome 79-91.
Test results and supporting details
See #24185. I tested on BrowserStack in Chrome versions 61, 62, 90, 91, 92, 95, and 104.
Chromium issue tracker - Status is "Fixed" - see comment 66 on May 21, 2021.