W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2009

Re: remedy for click event

From: Anne van Kesteren <annevk@opera.com>
Date: Sun, 20 Sep 2009 10:39:21 +0200
To: "Doug Schepers" <schepers@w3.org>, www-dom@w3.org
Message-ID: <op.u0jrnvxj64w2qv@annevk-t60>
On Sun, 20 Sep 2009 02:07:10 +0200, Doug Schepers <schepers@w3.org> wrote:
> For reasons I've already stated, I respectfully disagree with your  
> interpretation of "deprecated", and I don't intend to apply it in the  
> case of DOM3 Events.  While I am writing the spec for both authors and  
> implementers, the implications of deprecation most directly impact  
> implementers.  I already use the term "deprecated" in what I see as a  
> specific and pragmatic approach throughout the spec, and unless I hear  
> from implementers that they disagree with that use, I'm not going to  
> change it.

FWIW, I do find it somewhat confusing. I'm mostly familiar with this term  
due to HTML4 and there the end result was that UAs had to implement the  
deprecated features. This might not be the meaning HTML4 gave to it, I  
wouldn't know, but that is what it effectively meant.

I haven't checked the new DOM3 Events draft yet, but if not done so  
already, maybe explicitly indicate for each deprecated feature that it is  
also OPTIONAL for UAs to implement.

Having said that, while such an approach certainly works, I would  
personally prefer it if in the end we had a specification that does not  
include the optional features or explicitly excludes them from certain  
conformance classes, or something like that.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Sunday, 20 September 2009 08:40:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:03 GMT