The spec has been updated.
https://github.com/w3c/csswg-drafts/commit/c996510d75544786a5361127e69c71a5fc725785
—Myles
> On Jun 20, 2016, at 2:26 PM, Myles C. Maxfield wrote:
>
> All stable and nightly browsers that I could find[1] agree on the return of
> getComputedStyle() in this situation.
All stable and nightly browsers that I could find[1] agree on the return of
getComputedStyle() in this situation. Therefore, I opened this issue[2] to
update the spec to match the implementations.
—Myles
[1] - Microsoft Edge 25.10586.0.0 / Microsoft EdgeHTML 13.10586
- Firefox 50.0a1 (2016-06-2
Hello,
I asked this issue and W3C WG said that it means "used value". (
https://github.com/w3c/csswg-drafts/issues/190)
When I checked spec for getComputedStyle(), some properties('bottom',
'left', 'right', 'top')'s resolved value is the used value if the property
applies to a positioned element.
It looks like WebKit visually renders the result correctly according to the
spec text. Therefore, we are only interested here with the computed style of
the over-specified element.
The spec text uses the verb “becomes.” I don’t know if this means that either
1) the rendering and the computed st
Hello,
I'm working on blink engine as deokjin81@samsung.com.
And I have a question about implementation plan for getComputedStyle.
As I know, getComputedStyle does not handle over-constrained properties
correctly.
So I implemented it(
https://bugs.chromium.org/p/chromium/issues/detail?id=60111
5 matches
Mail list logo