- From: Glenn Adams <glenn@skynav.com>
- Date: Mon, 29 Apr 2013 01:30:49 -0700
- To: Sean Hayes <Sean.Hayes@microsoft.com>
- Cc: "public-tt@w3.org" <public-tt@w3.org>
Received on Monday, 29 April 2013 08:31:37 UTC
On Fri, Apr 26, 2013 at 5:59 AM, Sean Hayes <Sean.Hayes@microsoft.com>wrote: > A question from one of our developers who was asking what is the default > color for a textOutline value that specifies two lengths, but no color > value.**** > > ** ** > > My reading of the specification text is that in this case the outline > color takes the same value as the font color (which if not otherwise > specified by the author, is implementation dependent). This seems to us > somewhat less than useful in practice, and it might be better if the value > in this case were chosen by the implementation so as to create a high level > of contrast between the character and its background (e.g. black for a > white character on a transparent background).**** > > ** ** > > Not sure if anyone else has run into this? What do people think? > As Mike pointed out, the current spec text is unambiguous, so I think we need not do anything. Of course, this begs the question of why color is optional if the default is never particularly useful. I would not object to changing the syntax in 1.1 to make the color component non-optional.
Received on Monday, 29 April 2013 08:31:37 UTC