W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2010

Re: Last Call comment: Deprecation of DOMAttrModified [ISSUE-135]

From: David Bolter <david.bolter@gmail.com>
Date: Fri, 08 Oct 2010 11:58:23 -0400
Message-ID: <4CAF3F9F.3010804@gmail.com>
To: James Craig <jcraig@apple.com>
CC: Doug Schepers <schepers@w3.org>, www-dom@w3.org
  Unfortunately I couldn't make this call, and Monday is Thanksgiving in 
Canada so I can't promise to attend the follow up call. Would it make 
sense to split this into three proposals, such that the abstraction of 
desktop keyboard commands work is in one proposal, the a11y events in 
another, and the identification in a third?

What would be the pioneering implementation of all this? iPhone?


On 07/10/10 8:37 PM, James Craig wrote:
> FYI, the User Interface Independence proposal is going to be discussed on the W3C Hypertext Coordination Group (HCG) teleconference tomorrow morning. The group call is public tomorrow specifically for the sake of this discussion. Call-in info below.
>>>> Calling information:
>>>> Friday, October 8, 2010 13:00Z
>>>> (7am Pacific, 10am East Coast, 2 pm UK, 3 pm France)
>>>> Fixed time clock:
>>>> http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=14&year=200
>>>> 9&hour=14&min=0&sec=0&p1=0
>>>> Number to call:  +1.617.761.6200, conference code 4824 ("HTCG")
>>>> irc://irc.w3.org:6665/hcg or
>>>> http://www.w3.org/2001/01/cgi-irc
> On Oct 2, 2010, at 12:33 PM, Doug Schepers wrote:
>> Hi, James-
>> My apologies for not responding when you sent your earlier proposal. For some reason (perhaps because it had an attachment and I received several copies from different list), it ended up in my spam filter, so I didn't see it; thanks for bringing it to my attention.
>> I see several parts of your proposal which could be considered for inclusion in DOM3 Events, but it's not clear which parts apply to which specifications, or indeed, if your proposal might not be considered as a standalone accessibility spec that builds on DOM3 Events, HTML5, etc. For now, I've flagged DOMAttrChangeRequest as ISSUE-135 [1], since you call attention specifically to that.
>> UIRequestEvent, UIScrollRequestEvent, and UIValueChangeRequestEvent also struck me as possible additions to DOM3 Events, which I will could raise as separate issues if that's your intent.  (I quite like the UIRequestEvent, it seems simple to implement and generally useful.)
>> [1] http://www.w3.org/2008/webapps/track/issues/135
>> Regards-
>> -Doug Schepers
>> W3C Team Contact, SVG and WebApps WGs
>> James Craig wrote (on 9/20/10 8:22 PM):
>>> I have not received any response to this from the DOM group, and
>>> because DOM 3 has moved to Last Call, I want to make sure it's clear
>>> that this proposal was intended, in part, as an alternative for the
>>> deprecated DOMAttrModified in DOM 3.
>>> See DOMAttributeChangeRequestEvent, but please read it in the context
>>> of the larger document.
>>> http://lists.w3.org/Archives/Public/www-dom/2010JulSep/att-0106/UserInterfaceIndependence.html#DOMAttributeChangeRequestEvent
>>> On Mon, 30 Aug 2010, James Craig wrote
>>>> The following proposal is for consideration by the PF Working
>>>> Group, DOM Working Group, and HTML Working Group. It specifically
>>>> solves a few outstanding accessibility problems, but has much
>>>> broader implications, and could affect several recommendations,
>>>> including ARIA 2, DOM 3, and HTML 5. (Note: duplicate emails are
>>>> going out to a few relevant lists.)
>>>> Thanks, James Craig
>>>> http://lists.w3.org/Archives/Public/www-dom/2010JulSep/att-0106/UserInterfaceIndependence.html
Received on Friday, 8 October 2010 15:58:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:16 UTC