-
-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2022 Interoperability Chapter #3145
Conversation
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 8.7%, saving 2.42 KB.
1704 images did not require optimisation. |
….httparchive.org into interop-2022-chapter
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 27.5%, saving 377.04 KB.
1696 images did not require optimisation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bkardell I completed the edit in 72113da and updated the Staging link.
Nothing too controversial in the edit - mostly just cleaning up a few outstanding TODOs and making sure the commentary are after the figures (as per the Web Almanac style).
I think this is good to merge, apart from two comments I left for you. If happy we can remove those comments.
If I don't hear back from you by this time tomorrow, I'll merge this anyway so it's included in the release and then you can fix anything in a follow up PR.
src/content/en/2022/interop.md
Outdated
|
||
Flexbox is even older and more widely used. This year its use has grown again, [now appearing on 75% of mobile pages and 76% of desktop pages](./css#flexbox-and-grid-adoption). It has a similar number of tests to Grid and despite very wide adoption started in much worse shape. Entering 2021, some sub-features remained under-implemented, including: | ||
|
||
- Both Chrome and WebKit had issues with auto-height flex containers, leading to incorrectly sized images, which has now been resolved. {# TODO: Is this correct Brian? Added this to make it a sentence, as part of breaking up the list to allow the figures to be added #} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you check @bkardell
src/content/en/2022/interop.md
Outdated
|
||
- Both Chrome and WebKit had issues with auto-height flex containers, leading to incorrectly sized images, which has now been resolved. {# TODO: Is this correct Brian? Added this to make it a sentence, as part of breaking up the list to allow the figures to be added #} | ||
|
||
- CSS Box alignment defines several types of alignment. Among them [positional-alignment keyword values](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Box_Alignment#positional_alignment_keyword_values), which can be applied to justify-content and align-content and also to justify-self and align-self. These had ragged support and several interoperability issues. For absolute positioned flex items this was even worse. Again, these issues have been resolved. {# TODO: Again, is this correct Brian? Added this to make it a sentence, as part of breaking up the list to allow the figures to be added #} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And this
Going to merge this. We can follow up with separate PR. |
Fixes #2887
Staging URL: https://20220922t161618-dot-webalmanac.uk.r.appspot.com/en/2022/interoperability
Home page quotes: https://20220922t161618-dot-webalmanac.uk.r.appspot.com/en/2022/?feat=interoperability#featured-chapter
Initial conversion to markdown. There's still some open issues in the Doc and some pieces under discussion, but running short of time so thought I'd make a start on the conversion.
Assets: