- From: Brian Manthos <brianman@microsoft.com>
- Date: Tue, 1 May 2012 20:58:48 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- CC: Shane Stephens <shans@google.com>, "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
In animation cases, it effectively removes a feature (and adds a new one). As such "in the wild" we don't really have data yet because animations + gradients is new territory. We should probably at least have a note in CSS3 that it is likely the rule ordering will change in CSS4 so that authors have a warning now rather than having content break later. -Brian -----Original Message----- From: Tab Atkins Jr. [mailto:jackalmage@gmail.com] Sent: Tuesday, May 01, 2012 1:38 PM To: Brian Manthos Cc: Shane Stephens; L. David Baron; www-style list Subject: Re: [css3-images] interpolation of color stop positions (was Re: Change to currentColor means it's no longer animatable?) On Tue, May 1, 2012 at 12:58 PM, Brian Manthos <brianman@microsoft.com> wrote: > So CSS3 and CSS4 will have incompatible renderings? Changes happen. The question is how important those changes are, and how bad the "breakage" is. The original reason for not making the change was not that the change was bad, or that there was a lot of stuff that might break due to it, but only that the draft had changed a lot, should stop changing except for important things, and this wasn't an important change. Since that reason no longer applies, it's possible to make changes that are not too damaging. Note that the actual situations in which the swap would result in different renderings are quite small. You have to either explicitly put later stops before earlier stops, or mix length types such that the misordering happens automatically, and *then* mix either of those with implicitly-positioned stops. I've never seen a gradient in the wild that would trip these; while I don't doubt that they may exist, I argue they are very rare. ~TJ
Received on Tuesday, 1 May 2012 21:00:07 UTC