Intent to Implement: CSS Logical Properties: margin{-block,-inline}{-start,-end}

86 views
Skip to first unread message

Xing

unread,
Jan 10, 2017, 10:31:35 PM1/10/17
to blink-dev
xin...@intel.com https://drafts.csswg.org/css-logical-props-1/#logical-prop The CSS Logical Properties introduces margin{-block,-inline}{-start,-end}, which provide the author with the ability to control layout through logical, rather than physical, direction and dimension mappings.The related properties are: margin-block-start, margin-block-end, margin-inline-start, margin-inline-end. Provide the author with the ability to control layout through logical, rather than physical, direction and dimension mappings.change. Firefox: No public signals Edge: No public signals Safari: No public signals Web developers: No signals
Reference:
None. None. Yes. https://bugs.chromium.org/p/chromium/issues/detail?id=538475 https://www.chromestatus.com/features/5726839272112128 Yes.

PhistucK

unread,
Jan 11, 2017, 1:53:53 AM1/11/17
to Xing, blink-dev
Why no public signals from Firefox? They shipped it! :)
(I updated the ChromeStatus entry)

I would say the the web developer signals, while internal here, can be inferred from usage, for example, the Chrome web user interface (settings and other pages) uses (or used) the old versions (-webkit-margin-start or similar) extensively. This indicates that they are useful.
You can also infer signals from the metrics of -webkit-margin-start - over 2%, which means it is useful (though that could be due to internal Chrome usage :( It was not filtered up until a few weeks ago).

The Edge (well, Bing) metrics do not show a very high usage, but definitely not zero in a set of million websites.


PhistucK

--
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+unsubscribe@chromium.org.

Xing

unread,
Jan 11, 2017, 9:48:45 PM1/11/17
to blink-dev, xin...@intel.com
Thanks for point out, it is do shipped in FF.

A question about the return value of getComputedStyle:
From https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle, it says:
"The values returned by getComputedStyle are known as resolved values. These are usually the same as the CSS 2.1 computed values, but for some older properties like width, height or padding, they are instead the used values. "
"but CSS 2.1 redefined computed values as pre-layout, and used values as post-layout. "

And here, https://drafts.csswg.org/cssom/#resolved-values it says:
"getComputedStyle() was historically defined to return the "computed value" of an element or pseudo-element."

And in CSSComputedStyleDeclaration::getPropertyCSSValue, before return value, it will call document().updateStyleAndLayoutTreeForNode.
So for chromium, does it always return the computed value(document().updateStyleAndLayoutTreeForNode didn't trigger layout.)?


PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

Reply all
Reply to author
Forward
0 new messages