This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24297 - The canvas spec has huge differences from WHATWG HTML
Summary: The canvas spec has huge differences from WHATWG HTML
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.w3.org/html/wg/drafts/2dco...
Whiteboard:
Keywords:
Depends on: 21045
Blocks: 21046
  Show dependency treegraph
 
Reported: 2014-01-15 13:11 UTC by Masatoshi Kimura
Modified: 2014-03-23 01:52 UTC (History)
8 users (show)

See Also:


Attachments

Description Masatoshi Kimura 2014-01-15 13:11:47 UTC
For example, the W3C spec defines a constructor for the ImageData interface, but WHATWG's one is not.

Note that this is only a tiny example of gazillions of differences.

+++ This bug was initially created as a clone of Bug #21045 +++

I was totally confused by HTMLImageElement's named constructor.
If both spec editors won't work together, which spec do we have to follow?
(Of course you will say "The W3C's one." :)
It would be the nightmare if implementers have to watch both specs and determine which description is newer.
Comment 1 rcabanie 2014-03-23 01:52:12 UTC
Is this still an issue?
For the most part, the W3C level 2 and whatwg version of the spec should be in sync.