- From: Florian Rivoal <florian@rivoal.net>
- Date: Mon, 24 Nov 2014 21:53:55 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: www-style list <www-style@w3.org>
> On 24 Nov 2014, at 21:50, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > > On Mon, Nov 24, 2014 at 8:30 AM, Florian Rivoal <florian@rivoal.net> wrote: >> http://dev.w3.org/csswg/css-overflow-3/#overflow-properties >> >> For the computed value of ‘overflow’, the spec says "see individual properties”. However, that doesn’t help when the the computed values of individual overflow-x and overflow-y are different from each other, since overflow is a single valued property. >> >> A little bit of testing gives this: >> Chrome, Safari: auto >> Firefox, Presto: empty string >> IE: hidden+visible->visible, scroll+visible->scroll, auto+visible->visible > > Shorthands don't have computed values; they disappear during parsing. > The APIs that return a "computed value", like getComputedStyle, > actually return a string that, if re-assigned as style, will produce > the same computed value. When this isn't possible, as is sometimes > the case with shorthands, the correct answer is to return the empty > string, as specified in > <http://dev.w3.org/csswg/cssom/#serializing-css-values>. Oops, sorry for missing that. My little investigation used getComputedStyle, so Firefox and Presto are doing the right thing, while Chrome, Safari and IE are making stuff up? - Florian
Received on Monday, 24 November 2014 20:54:20 UTC