This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
For example, the WHATWG spec has the "resolution" attribute for the ImageData interface, but W3C'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 WHATWG's one." :) It would be the nightmare if implementers have to watch both specs and determine which description is newer.
What version of the W3C spec are you looking at?
(In reply to rcabanie from comment #1) > What version of the W3C spec are you looking at? The latest HTML Canvas 2D Context, Level 2 Nightly <http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas/>. Both of this spec and HTML Living Standard are updated daily which is really really confusing. Which is the latest? Why both continue to update with different content?
I agree that this sucks.
(In reply to Masatoshi Kimura from comment #2) > (In reply to rcabanie from comment #1) > > What version of the W3C spec are you looking at? > > The latest HTML Canvas 2D Context, Level 2 Nightly > <http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas/>. That one should be in sync with the WhatWG version. > the WHATWG spec has the "resolution" attribute for the ImageData interface, > but W3C's one is not. The HTML editors must have missed that. I will look into this. > Both of this spec and HTML Living Standard are updated daily which is really > really confusing. Which is the latest? What do you mean by latest? The latest proposed feature set (= WhatWG) or the spec that contains all implemented features? > Why both continue to update with different content? The version on the w3c site is a DRAFT and is not meant for public consumption. At some point in the future, the editors will make sure that the document validates and matches the WhatWG. We will then remove the features that are not implemented across browsers and publish a new spec. By continually integrating Ian's changes, we can catch integration issues now so we don't waste a lot of time later.
(In reply to Masatoshi Kimura from comment #0) > For example, the WHATWG spec has the "resolution" attribute for the > ImageData interface, but W3C's one is not. > Update: when I build the level 2 canvas spec locally, the resolution attribute is there. There seems to be an issue so the spec is not in sync.
I noticed the Latest Editor's Draft points [1] which is indeed in sync with WHATWG's one. When I filed this bug, I found [2] by googling. What is this? [1] http://www.w3.org/html/wg/drafts/2dcontext/master/ [2] http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas/
(In reply to Masatoshi Kimura from comment #6) > I noticed the Latest Editor's Draft points [1] which is indeed in sync with > WHATWG's one. When I filed this bug, I found [2] by googling. What is this? > > [1] http://www.w3.org/html/wg/drafts/2dcontext/master/ > [2] http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas/ good catch! The w3c server is using the wrong header with the 'html5_canvas' version. That is the proposed CR which reflects the state of about a year ago (give or take a couple of features)
Reassigning to rik since apparently the problem is on the W3C side. Please reassign to me if there's something I can fix. Thanks.
(In reply to Masatoshi Kimura from comment #6) > I noticed the Latest Editor's Draft points [1] which is indeed in sync with > WHATWG's one. When I filed this bug, I found [2] by googling. What is this? Those specs are there for the HTML editors so we can see that the w3c publishing system is working. (Most of us don't have direct access to the w3c servers.) They are not blessed releases but since you can find them through Google, we should make it clear what they contain.
Updating the summary according to the comment.
(In reply to Masatoshi Kimura from comment #10) > Updating the summary according to the comment. Please let me know if this is still an issue.