W3C home > Mailing lists > Public > public-html@w3.org > December 2007

Canvas gradients should not be optional

From: Philip Taylor <pjt47@cam.ac.uk>
Date: Fri, 14 Dec 2007 12:22:24 +0000
Message-ID: <47627580.6040600@cam.ac.uk>
To: HTML WG <public-html@w3.org>

The spec says:

   "Support for actually painting gradients is optional. Instead of 
painting the gradients, user agents may instead just paint the first 
stop's color."

Firefox, Opera and Safari support gradients. Rhino Canvas does too. The 
recent (unreleased) Konqueror with <canvas> also does gradients. 
ExplorerCanvas attempts to support gradients, despite getting them 
utterly wrong - presumably it was decided that buggy gradient support 
was better than conformingly following the spec's option of no 
gradients. I can't remember any other implementations now.

Optional features are harder to test, and a worse implementation (which 
lacks the feature entirely) could claim better conformance than a better 
implementation (which has the feature, and maybe fails in a few obscure 
edge cases). Since every implementer has decided to implement gradients, 
it seems there is no compelling reason to not implement it. So, the 
"Support for actually painting gradients is optional" paragraph should 
be removed.

-- 
Philip Taylor
pjt47@cam.ac.uk
Received on Friday, 14 December 2007 12:22:40 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:51 UTC