- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Fri, 12 Aug 2011 15:30:31 -0700
- To: Brian Manthos <brianman@microsoft.com>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Florian Rivoal <florianr@opera.com>, "www-style@w3.org" <www-style@w3.org>
I still don't understand. It seems simple enough on the surface to be able to determine e.g. what the 'start' side is, translate it to a physical side and proceed as normal. Or do you mean implementation-wise it is hard to track the value throughout the background and into the image? So far this is only about affecting the direction within the gradient itself, and not about affecting background property values such as 'background-position'. Does that make it harder to track? On Aug 12, 2011, at 2:37 PM, Brian Manthos <brianman@microsoft.com> wrote: > Backgrounds and writing mode intersecting will be an absolute nightmare. > > -Brian > > -----Original Message----- > From: Brad Kemper [mailto:brad.kemper@gmail.com] > Sent: Friday, August 12, 2011 2:12 PM > To: Brian Manthos > Cc: Tab Atkins Jr.; Florian Rivoal; www-style@w3.org > Subject: Re: [css3-images] new side-or-corner keywords? > > On Aug 12, 2011, at 1:08 PM, Brian Manthos <brianman@microsoft.com> wrote: > >> I'd prefer CSS.Never for start/end/before/after keywords and linear gradients > > Why is that? It is useful.
Received on Friday, 12 August 2011 22:31:16 UTC