<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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.<div class=""><br class=""></div><div class="">The spec text uses the verb “becomes.” I don’t know if this means that either 1) the rendering and the computed style should reflect this, or 2) just the rendering should reflect this.</div><div class=""><br class=""></div><div class="">Do you know if this issue has been discussed in the W3C?</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Myles</div><div class=""><div><blockquote type="cite" class=""><div class="">On May 27, 2016, at 5:59 AM, 김덕진 <<a href="mailto:dj0152@gmail.com" class="">dj0152@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hello, <div class=""><br class=""></div><div class="">I'm working on blink engine as <a href="mailto:deokjin81.kim@samsung.com" class="">deokjin81.kim@samsung.com</a>.</div><div class="">And I have a question about implementation plan for getComputedStyle.</div><div class="">As I know, getComputedStyle does not handle over-constrained properties correctly.</div><div class="">So I implemented it(<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=601118" class="">https://bugs.chromium.org/p/chromium/issues/detail?id=601118</a>) according to spec(<a href="https://www.w3.org/TR/2011/REC-CSS2-20110607/visuren.html#relative-positioning" title="" class="" rel="nofollow" style="font-size:11.726px;white-space:pre-wrap;color:rgb(0,0,204);word-wrap:break-word">https://www.w3.org/TR/2011/REC-CSS2-20110607/visuren.html#relative-positioning</a>) on blink engine.</div><div class=""><br class=""></div><div class="">Below paragraphs(from spec) describe detail operation to handle over-constrained properties.</div><div class=""><br class=""></div><div class="">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.<br class=""></div><div class=""><div class=""><br class=""></div><div class="">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').</div></div><div class=""><br class=""></div><div class="">I would like to know Webkit have any plan for this.</div><div class=""><br class=""></div><div class="">Thank you in advance,</div><div class="">Deokjin Kim</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><span style="font-family: sans-serif; font-size: inherit;" class=""><br class=""></span></div></div>
_______________________________________________<br class="">webkit-dev mailing list<br class=""><a href="mailto:webkit-dev@lists.webkit.org" class="">webkit-dev@lists.webkit.org</a><br class="">https://lists.webkit.org/mailman/listinfo/webkit-dev<br class=""></div></blockquote></div><br class=""></div></body></html>