- From: Philippe Wittenbergh <ph.wittenbergh@l-c-n.com>
- Date: Thu, 9 Jun 2011 08:58:16 +0900
- To: Brian Manthos <brianman@microsoft.com>
- Cc: Brad Kemper <brad.kemper@gmail.com>, Sylvain Galineau <sylvaing@microsoft.com>, "www-style@w3.org" <www-style@w3.org>, Tab Atkins Jr. <jackalmage@gmail.com>
On Jun 9, 2011, at 8:07 AM, Brian Manthos wrote:
> From: Brad Kemper [mailto:brad.kemper@gmail.com]
>> But anyone
>> using the keyword 'left' knows that it means 'from left to right', or they find
>> out within seconds and then move on.
>
> I disagree completely on this point. I constantly find this backwards notation a stumbling block. The reason I raised the issue is because I don't want to just "move on". The spec is broken and inconsistent, and I thought the goal of having drafts at all was to address such things so that the future can be better.
>
> Using that argument we might as well call it "foo" because "people will just learn that foo means that it progresses from left to right".
>
> Honestly, I think that would be better than using "left" to mean the exact opposite of "leftwards".
I always understood the keyword(s) to mean the starting point of the gradient, mimicking what keywords do for background-position, or for -maybe a better example- the keywords for positioning ('left' meaning 'build a block from the top left corner of its containing block' or pin a block on the left edge of the containing block and build/expand from there).
Those keywords also mean, in my understanding, that is where I'll see the first specified color of the gradient.
The original WebKit implementation meant as much, although in a much more verbose way: 'from left' etc.
I don't think I'm the only stylesheet author reading it that way.
The current wording of the editor draft is much more confusing to the designer-reader about this though, in my book.
Philippe
--
Philippe Wittenbergh
http://l-c-n.com/
Received on Wednesday, 8 June 2011 23:58:42 UTC