Ah true! I didn't consider the <length> values here. To mitigate this forward compat concern we can apply a partial mapping, e.g. if the current `vertical-align` property is set, it'll set the `baseline-source` to `auto`.
This should mitigate any forward compat concern here. I'll send a patch to do this tomorrow. This will allow us to perform the larger (complex, and risky) vertical-align changes in one shot later. Ian On Thu, Jan 12, 2023 at 6:20 PM fantasai <fantasai.li...@inkedblade.net> wrote: > On 1/12/23 17:21, Ian Kilpatrick wrote: > > Some additional context for folks: > > > > - Shipping the `baseline-source` property separately (this intent) > doesn't > > increase/decrease forwards compat risk in a material way - specifying it > would > > "win" over anything specified in `vertical-align` once we support that > > mapping, and addresses a large web developer concern. > > This is incorrect. In an implementation that implements the shorthanding > relationship vs an implementation that doesn't, the following two > declarations > will have different effects: > > .x { > baseline-source: first; > vertical-align: 10px; /* resets baseline-source to auto, or not */ > } > > ~fantasai > > -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJL3UpQ7QpGE2jJp6D26LT7dtt63tz_QU-cWqw7p%3D%2BULqSC-tg%40mail.gmail.com.
smime.p7s
Description: S/MIME Cryptographic Signature