This feature allows developers to align items within either flex or grid layout by their last baseline, instead of their first. This is done via the following properties: align-items: last baseline; /* flex/grid container */ justify-items: last baseline; /* grid container */ align-self: last baseline; /* flex/grid item */ justify-self: last baseline; /* grid item */
This feature will likely be difficult to use initially for web developers for a few reasons. Support and implementation status is patchy. While adding tests for this feature... https://wpt.fyi/results/css?label=master&label=experimental&aligned&view=subtest&q=flex-align-baseline%20or%20grid-align-baseline%20or%20grid-justify-baseline ...existing implementations typically only supported relatively simple cases well. This primarily was because various specifications which this feature interacts with didn't specify what the last baseline of various boxes should be. Additionally "@supports(align-items: last baseline)" will return true for many versions of browsers that don't have any (or partial) layout support for this feature. Web developers may rely on UA versions and/or javascript to check actual support.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
Basic CSS property debugging in DevTools.
108 or 109
We filed multiple issues related to this feature - primarily for all the different types of layout algorithms how to determine their last baseline was underspecified.
Scroll container - https://github.com/w3c/csswg-drafts/issues/7660
Flexbox - https://github.com/w3c/csswg-drafts/issues/7641
Multicol - https://github.com/w3c/csswg-drafts/issues/7639
Tables - https://github.com/w3c/csswg-drafts/issues/7655
Fieldset - https://github.com/w3c/csswg-drafts/issues/7656
(and more).
All of these issues have been resolved, and added tests.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJL3UpRb9dPstEirAv6pqspLgyab9%2B6bonCEzMrDNumkVH7S0g%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGH7WqFn76swgKd%3DguZJdXr656Ox5ZOG1SQwDB%2B877L9G08JRw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfVo7bM0GHGuvcwcCNuuAbE0%3DH6tipmcHzsqPybCXFtsKg%40mail.gmail.com.
Quick question on the levels of support. You mention that Firefox
has basic support. And WebKit landed some support in
https://github.com/WebKit/WebKit/pull/4799. Do you have a sense of
how Safari's implementation (maybe testable in nightly builds)
compares to Firefox and your implementation?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJL3UpSeh7ut1KYx-uSMK7_uS2EkVPF8fa-Ku5ucMELx3JfR4Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a3ebb96-40c9-615c-2c8e-8bf2e844de65%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJL3UpTgOPZFJcB3DxU7B5Qe0soN%3Do5tV-TcQcntNm8bprc%2BoQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYctYhJLcFGyPD2uZ1D%3Ds7%2BHjXJe4BBLR43b68hwxiMjRA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a74589bf-80d2-7d80-4680-f47100c24b2d%40chromium.org.