Re: ISSUE-213 (text outline): Advance notice of deprecation for textOutline [TTML.next]

Concur to be silent for now.

Sent from my phone

On May 23, 2013, at 4:56 PM, Glenn Adams <glenn@skynav.com> wrote:

> I'd suggest we not do anything in SE, and that in the mapping we define in .next, we simply map to text-shadow in the HTML/CSS mapping rules. I think the absence of literal support for 'text-outline' in browsers doesn't affect this usage.
> 
> 
> On Thu, May 23, 2013 at 2:45 PM, Pierre-Anthony Lemieux <pal@sandflow.com> wrote:
>> > I suggest we put a note in the SE to the effect that we intend to deprecate this in v.next and replace it in v-next with textShadow.
>> 
>> Do you mean only in the context of a mapping to HTML, not in general?
>> 
>> Thanks,
>> 
>> -- Pierre
>> 
>> On Thu, May 23, 2013 at 6:32 AM, Michael Dolan <mdolan@newtbt.com> wrote:
>> > Ok in concept for v. Next but object to any hint that a decoder would be permitted to ignore the current attribute.
>> >
>> > Sent from my phone
>> >
>> > On May 23, 2013, at 6:55 AM, "Timed Text Working Group Issue Tracker" <sysbot+tracker@w3.org> wrote:
>> >
>> >> ISSUE-213 (text outline): Advance notice of deprecation for textOutline [TTML.next]
>> >>
>> >> http://www.w3.org/AudioVideo/TT/tracker/issues/213
>> >>
>> >> Raised by: Sean Hayes
>> >> On product: TTML.next
>> >>
>> >> All of the major browsers have declined to implement text-outline, and as a result it is dropped from CSS3. Instead they have adopted text-shadow which is probably sufficient for our needs.
>> >>
>> >> e.g. try :
>> >> .region {
>> >>      background-color:grey;
>> >> }
>> >> p {
>> >>    color:white;
>> >>    text-shadow: 0px 0px 1px black , 0px 0px 3px black, 0px 0px 3px black;
>> >> }
>> >>
>> >> I suggest we put a note in the SE to the effect that we intend to deprecate this in v.next and replace it in v-next with textShadow.
>> >>
>> >>
>> >>
>> >>
>> >
>