Ian,
So, are you telling me that the WhatWg will not make its way in to the W3C
spec? Note: I am not copying anything. I am simply commenting on what was
put in FF.
Also, if you are asking for our input you are asking for our contributions.
As you can see there are problems with the current WhatWG spec.
I did not make the decision to use the WhatWG implementation.
Rich
Rich Schwerdtfeger
From: Ian Hickson <ian@hixie.ch>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc: Dominic Mazzoni <dmazzoni@google.com>, Rik Cabanier
<cabanier@gmail.com>, Alexander Surkov
<surkov.alexander@gmail.com>, "public-canvas-api@w3.org"
<public-canvas-api@w3.org>, Mark Sadecki <mark@w3.org>, Jay
Munro <jaymunro@microsoft.com>
Date: 02/17/2014 12:13 PM
Subject: Re: hit regions Firefox support update
On Mon, 17 Feb 2014, Richard Schwerdtfeger wrote:
>
> We have been discussing this with W3C Canvas API editors.
They're not the ones who designed or are maintaining the hit region API.
It's one thing for the W3C to just copy everything the WHATWG does and
republish it as a W3C spec. It's orders of magnitude worse when you first
copy it all, *and then start changing it without coordinating with the
group that first developed it*.
Either make up your own APIs from scratch, or work with the group that's
designing the APIs that you copy when you review them. Don't just copy
someone else's work, then start changing it without coordination. This
results in forked technologies and is actively harming the Web.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
