Update per Netflix whitepaper

[palemieux]

Closes #8
Closes #3

Also refactored tts:textShadow per https://www.w3.org/AudioVideo/TT/tracker/issues/234

[nigelmegitt]

Question asked about FCC requirements.

[nigelmegitt]

Is this genuinely a requirement of FCC that is not currently met with textOutline? I thought that had already been deemed sufficient.

[palemieux]

@mikedo What say you?

[andreastai]

There are some issues with tts:textOutline but I can not remember what they have been. Possibly we can look at some examples.

[palemieux]

There are some issues with tts:textOutline but I can not remember what they have been. Possibly we can look at some examples.

Per the joint CSS/TTWG meeting, text-outline is not well-supported in UAs today. No one disputed the value of the feature however -- as I recall.

[nigelmegitt]

Yes, that's what I recall - the problem with tts:textOutline is not that it is a poor fit for the requirement, but that it is not widely implemented. If it were implemented, presumably support for #textShadow would no longer be required to support the edge styles required by FCC?

[cconcolato]

rubyAlign should be 'auto' only if it means center, otherwise 'center' should also be allowed. The white paper was not so clear.

rubyPosition 'auto' would be fine if defined to map 'outside'

I think it misses writing-mode.

[palemieux]

I think it misses writing-mode.

@cconcolato writingMode is already allowed in IMSC 1.1

[palemieux]

rubyPosition 'auto' would be fine if defined to map 'outside'

@cconcolato Why not constrain rubyPosition="outside" then? Or do you mean that both auto and outside need to be allowed.

[palemieux]

rubyAlign should be 'auto' only if it means center, otherwise 'center' should also be allowed. The white paper was not so clear.

@cconcolato Should we constrain rubyAlign="center" then? Or do you mean that both auto and center need to be allowed?

[cconcolato]

For rubyPosition and rubyAlign, we care for the default behavior, whatever the keyword value is.

[cconcolato]

LGTM

[mikedo]

@nigelmegitt Is this genuinely a requirement of FCC that is not currently met with textOutline? I thought that had already been deemed sufficient.

textShadow better matches the FCC requirements than textOutline, but I need time to study whether textShadow alone is sufficient.