Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No information provided| Shipping on desktop | 156 |
| Shipping on Android | 156 |
| Shipping on WebView | 156 |
| Shipping on iOS | 156 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
No information provided--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9a88d4e0-ee44-421d-bbb5-3aab64089854n%40chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
LGTM3
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/33fe8e41-c8bd-4763-b572-6dca5537570bn%40chromium.org.
Quick correction to this I2S: jsnkuhn caught that the corner shorthands in Chromium still used the earlier per-corner, slash-separated grammar, rather than the current CSS Borders 4 grammar (corner: <'border-radius'> || <'corner-shape'>). The existing WPTs encoded the old grammar too, so passing tests did not catch this. Sorry I missed it before the flag flip.
I reverted the enable CL (https://crrev.com/c/8494091); CSSCornersShorthand is experimental again.
The Chromium parser, serialization, and WPT fix is soon under review at https://crrev.com/c/8498274 .
The WebKit implementation I mentioned earlier (https://github.com/WebKit/WebKit/pull/65464) also used the old grammar, behind a default-off flag. I’m preparing a WebKit follow-up as well.
Sorry for the churn. I do my best to catch these things, but with the number of moving parts and spec issues involved, mistakes still happen. In the jungle of spec issues, I sometimes lose sight of the trees.
is there anything i have to edit on the feature entry to kinda like "halt" it?
Quick correction to this I2S: jsnkuhn caught that the corner shorthands in Chromium still used the earlier per-corner, slash-separated grammar, rather than the current CSS Borders 4 grammar (corner: <'border-radius'> || <'corner-shape'>). The existing WPTs encoded the old grammar too, so passing tests did not catch this. Sorry I missed it before the flag flip.
I reverted the enable CL (https://crrev.com/c/8494091); CSSCornersShorthand is experimental again.
The Chromium parser, serialization, and WPT fix is soon under review at https://crrev.com/c/8498274 .The WebKit implementation I mentioned earlier (https://github.com/WebKit/WebKit/pull/65464) also used the old grammar, behind a default-off flag. I’m preparing a WebKit follow-up as well.
Sorry for the churn. I do my best to catch these things, but with the number of moving parts and spec issues involved, mistakes still happen. In the jungle of spec issues, I sometimes lose sight of the trees.
is there anything i have to edit on the feature entry to kinda like "halt" it?
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bcc3c056-3a1c-4b31-9641-124c81157206n%40chromium.org.