W3C home > Mailing lists > Public > www-style@w3.org > July 2011

RE: [css3-images] remaining gradient issues

From: Brian Manthos <brianman@microsoft.com>
Date: Tue, 26 Jul 2011 19:17:07 +0000
To: Brad Kemper <brad.kemper@gmail.com>, www-style list <www-style@w3.org>
Message-ID: <9710FCC2E88860489239BE0308AC5D170F9847@TK5EX14MBXC264.redmond.corp.microsoft.com>
I'll leave it to Tab to capture the resolutions from Monday


Regarding corner-to-corner gradient renderings (regardless of syntax)...
I recommend (in v3 or v4 of images module) changing the mapping of corner gradients as follows:
(1) the "gradient line" has a slope of w/h or -w/h depending upon which "ordered corner pair" is indicated
(2) the "gradient segment" is a portion of the gradient line which (a) has a center point in the middle of the box and (b) has length equal to the length of the diagonal of the box
(3) the "gradient vector" is the defined as the gradient segment with one of the "end points" designated as a start point
(4) the rendering for corner-to-corner linear gradients is identical to the rendering produced when using the alternate (angle) syntax with the angle embedded in the "gradient vector"

Note to spec editors:
Note my use of 2 new terms: "gradient segment" and "gradient vector".  We should consider revisiting all references to "gradient line" in the specification.  Some of them have length and location (and thus are segments) and some have direction (and thus are vectors).


Regarding Brad's proposal "add 'from' keyword"...An equally attractive and unattractive proposal is to add the 'to' keyword instead.  I recommend against both approaches.


"From an author's point of view" the behavior of prefixed properties should not directly impact the future progression of non-prefixed properties.  This has been stated, in various forms and forums, repeatedly.  If that becomes not the case, then why do we have prefixes in the first place?

Recommendation to Brad:
Propose a change to the W3C prefixes usage policy that directly and clearly addresses the problem you're finding (and paraphrased poorly: ) "early adopters that use prefixes have issues with stuff that changes for long-approval-process specs".  As I understand the current spec development model, prefixes provide a realm for exploration *not* a trustworthy content production environment.
Received on Tuesday, 26 July 2011 19:17:36 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:42 GMT