[whatwg] return lowercase hex values for fillStyle and strokeStyle
contact at nickshanks.com
Thu May 10 00:02:52 PDT 2007
On 10 May 2007, at 07:31, Ian Hickson wrote:
> On Tue, 29 Aug 2006, Anne van Kesteren wrote:
>> Instead of returning an uppercase six digit hex value I suggest
>> returning a lowercase value for compatibility with what UAs
>> IE) currently do for CSS already and what Mozilla already does for
> On Tue, 5 Sep 2006, Christoph Päper wrote:
>> It may be the right decision on compatibility grounds, but other than
>> that lowercase hexadecimal digits (0-9, a-f) are almost always a bad
>> choice, because a, c and e have no ascenders like every hindu-arabic
>> decimal digit has and thus make the number harder to read. This
>> obviously does not apply to fonts with old-style numerals aka. text
>> figures, where 0, 1 and 2 have neither ascenders (like 6 and 8) nor
>> descenders (like 3, 4, 5, 7 and 9), but those are rather unlikely
>> to be
>> used in a programming environment.
> You can use uppercase letters when setting, which is where you're most
> likely to see this. It only affects the getter.
> I think consistency with the rest of the platform will get us at
> least as
> much of a win for authors as would be gotten from uppercase letters.
Would it not make more sense to fix the UAs.
lower-case hex is horrible to read.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2157 bytes
Desc: not available
More information about the whatwg