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=601118) according to
spec(
https://www.w3.org/TR/2011/REC-CSS2-20110607/visuren.html#relative-positioning)
on blink engine.

Below paragraphs(from spec) describe detail operation to handle
over-constrained properties.

If neither 'left' nor 'right' is 'auto', the position is over-constrained,
and one of them has to be ignored. If the 'direction' property of the
containing block is 'ltr', the value of 'left' wins and 'right' becomes
-'left'. If 'direction' of the containing block is 'rtl', 'right' wins and
'left' is ignored.

The 'top' and 'bottom' properties move relatively positioned element(s) up
or down without changing their size. 'Top' moves the boxes down, and
'bottom' moves them up. Since boxes are not split or stretched as a result
of 'top' or 'bottom', the used values are always: top = -bottom. If both
are 'auto', their used values are both '0'. If one of them is 'auto', it
becomes the negative of the other. If neither is 'auto', 'bottom' is
ignored (i.e., the used value of 'bottom' will be minus the value of 'top').

I would like to know Webkit  have any plan for this.

Thank you in advance,
Deokjin Kim
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Reply via email to