ISSUE-208: Define behavior for unsupported colors.
Define behavior for unsupported colors.
- Raised by:
- Glenn Adams
- Opened on:
- tts:color (and other properties that use colors) don't define what a presentation processor should do if a specific color isn't supported; as such, this means that the default semantics of XSL-FO or CSS2 hold;
we should consider defining something specific or add a note that references the interpretation of unsupported colors in XSL-FO or CSS2 as appropriate
- Related Actions Items:
- No related actions
- Related emails:
- No Meeting today 12-09-13 (from Sean.Hayes@microsoft.com on 2013-09-12)
- Minutes for 05/09/13 (from firstname.lastname@example.org on 2013-09-05)
- Agenda for 05/09/13 (from email@example.com on 2013-09-04)
- RE: TTML Agenda for 29/08/13 (from firstname.lastname@example.org on 2013-08-28)
- TTML Agenda for 29/08/13 (from email@example.com on 2013-08-28)
- ISSUE-208 (unsupported colors): Define behavior for unsupported colors. [TTML.next] (from firstname.lastname@example.org on 2013-05-15)
I see the following language in 8.3.2:
"If a presentation processor does not support a specific, valid color or alpha value, then it must interpret it as being equal to the closest supported value."
This may be adequate to close this issue.
Added further note in 8.3.5:
"In this context, the phrase closest supported value means the value for which the Euclidean distance between the computed color or alpha and the supported color or alpha in the RGB color space is minimized."
I believe this address this issue. See https://dvcs.w3.org/hg/ttml/rev/24ed1e6adcdd.
Display change log