- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Fri, 10 May 2013 12:24:46 -0700
- To: Lea Verou <lea@w3.org>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Sebastian Zartner <sebastianzartner@gmail.com>, Sam L'ecuyer <sam@cateches.is>, François REMY <francois.remy.dev@outlook.com>, Jake Archibald <jaffathecake@gmail.com>, Šime Vidas <sime.vidas@gmail.com>, www-style list <www-style@w3.org>
On May 10, 2013, at 11:52 AM, Lea Verou <lea@w3.org> wrote: > There is discussion in the FXTF (and I think it's made it into the ED as well) to apply filters only to specific areas of an element such as borders, shadows or backgrounds. Argh. Top posting is a no no. Anyway, yes, I hope filters will have that. Eventually. In which case, 'color-adjust' would just be a limited shorthand for that, I guess. > On May 10, 2013, at 21:44, Tab Atkins Jr. wrote: > >> On Fri, May 10, 2013 at 11:23 AM, Lea Verou <lea@w3.org> wrote: >>> On May 10, 2013, at 21:11, Tab Atkins Jr. wrote: >>>> I can see the potential for a property that adjusts the computed-value >>>> of other color properties in this way. Call it 'color-adjust', have >>>> its value be a number of property names and color-adjusters like what >>>> color() has, in a comma-separated list. >>> >>> What use case does this cover that CSS Filters do not? >> >> It seems completely unrelated. If you just want to adjust the >> border-color of a box on hover, for example darkening it to indicate >> that it's "ready to be clicked", you can't do that with CSS filters. >> >> ~TJ >
Received on Friday, 10 May 2013 19:25:24 UTC