Intent to Implement and Ship: CSS flow-relative margins, paddings and borders

75 views
Skip to first unread message

Oriol Brufau

unread,
Jun 6, 2018, 9:38:20 AM6/6/18
to blink-dev
Contact emails

Spec

Summary
Implement the flow-relative margin, padding and border longhand properties introduced by CSS Logical Properties.
They are already supported but using non-standard names with a -webkit- prefix.
The properties with the standard names would be implemented, and the prefixed ones would become aliases.

Motivation
Provide the author with the ability to control layout through logical, rather than physical, direction and dimension mappings.

On top of that, this will make it easier to share tests with Firefox in the implementation of new specifications.
For example, Firefox uses these properties extensively to test CSS Grid Layout, it'd be nice to have them available in Chromium to verify interoperability.

Interoperability risk
Firefox: Shipped.
Edge: Under Consideration, High Roadmap Priority
Safari: No public signals
Web developers: Some people are using PostCSS (there are few plugins there) to use these properties already due to lack of browsers support.

Tests for these new properties were added into the WPT suite in https://github.com/web-platform-tests/wpt/pull/11324 

Compatibility risk
The existing prefixed properties will continue working as aliases, so the risk is minimal.
However, they will now serialize like the new properties.

Ongoing technical constraints
None.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux,
Chrome OS, Android, and Android WebView)? 
Yes.

OWP launch tracking bug

Link to entry on the Chrome Platform Status

Requesting approval to ship?
Yes.

Rick Byers

unread,
Jun 6, 2018, 12:59:11 PM6/6/18
to obr...@igalia.com, blink-dev
There's an earlier intent here for a superset of this work which already has an LGTM1 from foolip, so I assume (unless he says otherwise) that still applies.

Unprefixing these LGTM2, thank you!


--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ccbe1280-3b42-41be-1394-e5edee9243a8%40igalia.com.

Yoav Weiss

unread,
Jun 6, 2018, 1:11:37 PM6/6/18
to Rick Byers, obr...@igalia.com, blink-dev
LGTM3

Can you also add use-counters (if there aren't already) to the prefixed version do that we'll have data on their usage and maybe one day be able to remove them?

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/CAFUtAY_d4MG1GV39q3VZjk1-1p%2B%2Bc%3DFoHB%3DwfV7cM2qM%3DALAzQ%40mail.gmail.com.

Rick Byers

unread,
Jun 6, 2018, 2:04:01 PM6/6/18
to Yoav Weiss, obr...@igalia.com, blink-dev
Good idea!  In general all of our prefixed APIs should either be on a path to removal, or something we should spec as part of the web platform (worst case, in the compat spec if the spec for the unprefixed versions isn't interested in documenting reality).

Oriol Brufau

unread,
Jun 6, 2018, 4:21:41 PM6/6/18
to Yoav Weiss, Rick Byers, blink-dev

Yes, there are counters for the prefixed properties already, and there will be counters for the new properties too.

Once the standard properties are shipped, we can send an intent to deprecate or remove the prefixed ones, whichever is appropriate.

-- Oriol Brufau


El 6/6/18 a les 19:11, Yoav Weiss ha escrit:
Reply all
Reply to author
Forward
0 new messages