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

Re: [css-text] text-shadow and inset

From: Brad Kemper <brad.kemper@gmail.com>
Date: Sun, 28 Jul 2013 09:34:46 -0700
Message-Id: <A6CE6003-0B1D-4170-8B4C-0BC771C2CE72@gmail.com>
Cc: Simon Fraser <smfr@me.com>, www-style list <www-style@w3.org>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
On Jul 28, 2013, at 9:11 AM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:

> On Sat, Jul 27, 2013 at 1:03 PM, Simon Fraser <smfr@me.com> wrote:
>> On Jul 26, 2013, at 10:16 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>>> Due to persistent developer requests, we're planning on implementing
>>> 'inset' for text-shadow in Blink.  Does anyone have any strong
>>> objections?  If not, can we update css-text (either level 3 or 4, I'm
>>> not picky) to allow the keyword?
>>> (It turns out that Skia has some features that make this not too hard
>>> to implement in a performant manner, at least upon initial review.)
>> I object unless you can specify the behavior of inset in terms of bezier path manipulations
>> that can be performed by most graphics libraries.
> Ignoring spread (which we aren't planning to add yet), there's no need
> to specify anything special here.  To do an inset you just do a normal
> shadow,

invert the alpha,

> clip it by the text path, and paint it at a different layer.

Yes. You said it more succinctly than I did, and only left out one small step.

> (I'd like spread for text-shadows, but that's irrelevant to the topic at hand.)
Received on Sunday, 28 July 2013 16:35:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:32 UTC