Heh. There's clearly still a good deal of confusion about what the intended
behavior here is. Well, I'm confused anyways. :)
On Fri, Nov 5, 2010 at 9:32 PM, James Craig jcr...@apple.com wrote:
Ojan Vafai wrote:
How is [ DOMAttributeChangeRequestEvent ] any different than
DOMAttrModified? The
On Nov 10, 2010, at 3:40 PM, Ojan Vafai wrote:
Heh. There's clearly still a good deal of confusion about what the intended
behavior here is. Well, I'm confused anyways. :)
On Fri, Nov 5, 2010 at 9:32 PM, James Craig jcr...@apple.com wrote:
Ojan Vafai wrote:
How is [
On Fri, Nov 5, 2010 at 6:32 PM, James Craig jcr...@apple.com wrote:
Ojan Vafai wrote:
How is [ DOMAttributeChangeRequestEvent ] any different than
DOMAttrModified? The spec claims it doesn't have the problems that
DOMAttrModified has, but I don't see how that's the case.
DOMAttrModified
On Fri, Nov 5, 2010 at 6:40 PM, James Robinson jam...@google.com wrote:
On Fri, Nov 5, 2010 at 6:32 PM, James Craig jcr...@apple.com wrote:
Ojan Vafai wrote:
How is [ DOMAttributeChangeRequestEvent ] any different than
DOMAttrModified? The spec claims it doesn't have the problems that
I don't think calling these Request events fits with the rest of the web
platform. Essentially, these are events that fire before some action occurs
and gives the web developer the opportunity to cancel that action. The
precedence in web events is to call those before* events. So, instead of
On Mon, Nov 1, 2010 at 1:03 PM, Chris Fleizach cfleiz...@apple.com wrote:
You reviewed- the first pass at an implementation of this proposal
Sorry for not responding sooner.
https://bugs.webkit.org/show_bug.cgi?id=47301
but haven't responded to this thread. Do you have any other
On Nov 2, 2010, at 12:48 PM, Ojan Vafai wrote:
On Oct 27, 2010, at 2:57 PM, James Craig wrote:
James Craig responded:
The main difference seems to be that our Undo and Redo *request* allows
the web application to determine what (if anything) should be undone, or
redone, where the HTML5
Hi Ojan,
You reviewed- the first pass at an implementation of this proposal
https://bugs.webkit.org/show_bug.cgi?id=47301
but haven't responded to this thread. Do you have any other objections.
On Oct 27, 2010, at 2:57 PM, James Craig wrote:
Sorry for the delayed response, Tony. My answers
Sorry for the delayed response, Tony. My answers inline.
On Sep 3, 2010, at 9:35 AM, Tony Chang wrote:
I'm curious what elements the UIRequestEvents apply to. Does it fire at the
document level or does it fire for specific elements like textareas?
Focused element (or AX-focused element)
From: cfleiz...@apple.com
Date: Thu, 2 Sep 2010 17:34:07 -0700
To: webkit-dev@lists.webkit.org
CC: jcr...@apple.com
Subject: [webkit-dev] W3C Proposal: User Interface Independence for
Accessible Rich Internet Applications
Hello WebKit,
James and I
Hi Chris,
I'm curious what elements the UIRequestEvents apply to. Does it fire at the
document level or does it fire for specific elements like textareas? The
addition of undo/redo is similar to the proposal to add this to the
textInput event. There was some discussion of that here:
Sorry for not reading the document in detail, but are these events
fired synchronously or asynchronously?
Adam
On Thu, Sep 2, 2010 at 5:34 PM, Chris Fleizach cfleiz...@apple.com wrote:
Hello WebKit,
James and I have been working on a W3C proposal to address some shortcomings
we've noticed
On Sep 3, 2010, at 12:13 PM, Adam Barth wrote:
Sorry for not reading the document in detail, but are these events
fired synchronously or asynchronously?
Since it's all client-side communication between the web app and local user
agent, I don't have a preference. Chris may. Do you?
On Sep 3, 2010, at 5:25 AM, Mike Marchywka wrote:
Certainly an ability to zoom text is well known, but a text to
speech facility or re-rendering from web author's original
intent ( text to audio conversion) could be of general interest.
[ I guess this also motivates another general rant I
On Fri, Sep 3, 2010 at 1:30 PM, James Craig jcr...@apple.com wrote:
On Sep 3, 2010, at 12:13 PM, Adam Barth wrote:
Sorry for not reading the document in detail, but are these events
fired synchronously or asynchronously?
Since it's all client-side communication between the web app and local
Nothing I'm aware of would cause this to be synchronous. Thanks for pointing it
out. It's definitely worth mentioning this fact in the proposal
On Sep 3, 2010, at 4:56 PM, James Craig wrote:
On Sep 3, 2010, at 1:47 PM, Dominic Mazzoni wrote:
On Fri, Sep 3, 2010 at 1:44 PM, Adam Barth
16 matches
Mail list logo
