My general position is that no style value returned via getComputedStyle() should be 'auto' if there is a legal return value that denotes the "resolved" or "as used" interpretation of 'auto'. On Mon, Apr 29, 2013 at 1:48 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 4/29/13 4:46 PM, Tab Atkins Jr. wrote: > >> On Mon, Apr 29, 2013 at 1:42 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: >> >>> On 4/29/13 4:22 PM, Sylvain Galineau wrote: >>> >>>> >>>> returning the computed value is the interop behavior in this case. >>>> >>> >>> Except it's not in general: ff the specified value is "auto", browsers >>> don't >>> return "auto"... >>> >> >> Note that "auto" is resolvable at computed-value time (unless the >> other side is a percentage). >> > > While true, that's not how those computed values are currently defined. > Whether they should be is a separate question, that affects not just > getComputedStyle but also inheritance.... (Not that I expect it's common to > do "left: inherit" outside conformance tests!) > > -Boris > >Received on Monday, 29 April 2013 21:00:15 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:29 UTC