W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2007

[whatwg] Compatibility problems with HTML5 Canvas spec.

From: Philip Taylor <excors+whatwg@gmail.com>
Date: Tue, 25 Sep 2007 22:19:47 +0100
Message-ID: <ea09c0d10709251419i630222fch183cc846bc252191@mail.gmail.com>
On 25/09/2007, Oliver Hunt <oliver at apple.com> wrote:
> Firefox 2/3 and Safari 2 clear the context's path on strokeRect/
> fillRect, this violates the spec -- but there are many websites that
> now rely on such behaviour despite the behaviour defined in hmtl5.
> This means that those browsers that match the current draft (eg.
> Safari 3 and Opera 9.x) fail to render these websites "correctly".

How hard would it be to get those sites fixed? If there are problems
in something like PlotKit or Reflection.js, which lots of people copy
onto their own servers, then it would be a pain to break
compatibility. If it's just sites like canvaspaint.org where there is
a single copy of the code and the developer still exists and can
update it, it seems a much less significant problem to break
compatibility.

> Unfortunately it isn't really an edge case as it's a relatively
> common occurance -- people expect that the rect drawing function (for
> example) will clear the path, so expect clearRect
> (myCanvasElement.width, myCanvasElement.height) to clear the rect and
> reset the path, and other similarly exciting things :-/

Firefox also resets the path on drawImage and putImageData, unlike
Opera and Safari 3 - do people depend on that behaviour too?

> --Oliver

-- 
Philip Taylor
excors at gmail.com
Received on Tuesday, 25 September 2007 14:19:47 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:57 UTC