Hi,
few comments,
to make it easier to integrate the testsuite to other test systems
(like mochitest), it might be useful to use some prefix in function and
global variable names. Maybe w3c_ or dom3event_ ?
Also, tests should be as automatic and as autonomic as possible - so
shouldn't depend
Hi all,
the draft says that the initial value for upload complete flag is false
and then there are several ways to get it set to true. But when is the
value set back to false if XHR object is reused?
Perhaps '3.5.3 Initiating a Request', right after step 2?
-Olli
Hi all,
currently per the draft 'abort' and 'error' events are always
dispatched to .upload, even if there isn't anything to upload.
'loadstart', 'progress' and 'load' are dispatched only if
request entity body is not empty.
I think the same restriction should apply to 'abort' and 'error' too.
Hi,
perhaps the test style could be something like in the attached file,
in which I modified your original test a bit.
The idea is that vendor could provide vendor_functions.js which defines
functions to integrate test to vendor's own test system.
-Olli
Carmelo Montanez wrote:
Hi:
Given
Chapter 5.4.4.3. Events and the Window object [1] says that event is
also dispatched to window before (and after) dispatching to DOM
nodes. I'd rather say window object is part of the event target chain
(unfortunately load event is a special case), so events automatically
propagate from
Jonas Sicking wrote:
Ian Hickson wrote:
On Thu, 7 Aug 2008, Olli Pettay wrote:
Could we actually just say that if document implements DocumentView
interface and .defaultView isn't null and implements EventTarget, the
event propagates to .defaultView. So in that case defaultView becomes
Jonas Sicking wrote:
Is that any load event, or only specific load events? (i.e. is it a
characteristic of the bubbling/capture process, or the events that are
fired by certain circumstances like the end of parsing or an image
being fetched from the network?) If the latter, it would be
Ian Hickson wrote:
DOM2 Traversal and Range has a number of problems, and really needs a
rewrite. However, in the absence of the resources to do that, I realised
that we could settle for releasing some errata. Arguably we as a working
group have somewhat the authority to do that, so here's a
Garrett Smith wrote:
Are you asking: What if the loadend handler calls open() on the same
connection in loadend?
Right.
When loadend is called, the actual completion event (abort | fail
| load ) has not fired.
Calling open should cause the previous connection to end. Jonas
suggested that
(as a legacy
event, not obligatory to implement), there is still need to define what
its .wheelDelta means, because that doesn't tell how many lines or how
many pixels to scroll.
-Olli
Olli Pettay wrote:
Hi all,
there has been some discussion about how wheel event should work, and
what kind
So I think those NIST_ prefixes should be
vendor_ in js. That way any vendor could hopefully easily integrate
tests to their system by providing vendor_ functions.
Those could be called something else too, sure. Maybe
integration_point_XXX or hopefully something shorter.
Is there a reason to
On 11/07/2008 12:03 AM, Travis Leithead wrote:
I recently found an email thread from wy back where some internal folks at
Microsoft had come to the IE team asking about our support for Mutation Events.
They had a concern with the current DOM L3 Spec's DOMCharacterDataModified
event
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Olli Pettay
Sent: Wednesday, October 01, 2008 4:46 AM
To: public-webapps@w3.org
Subject: Re: Wheel events
Hi all,
So version 3 got implemented in Mozilla, but in a bit modified way.
There are separate events
Hi Travis,
On 12/09/2008 02:15 AM, Travis Leithead wrote:
Pixel scrolling / line scrolling aren't intended purpose. They are describing
the data browser gets from the operating
system.
At least on Windows-OS, this binding of pixel/line scrolling to a wheel event
does not exist. I think
On 12/27/08 2:17 AM, Kartikaya Gupta wrote:
Found an issue in DOM2 Range that doesn't seem to be addressed anywhere that I
could find:
Section 2.12.1 (handling insertions) says that the boundary point offset should only be adjusted if the
insertion point's offset is strictly less than it.
On 2/2/09 5:39 PM, Charles McCathieNevile wrote:
Hi,
It would be nice to get DOM 3 Events rolling again. Doug is away for
three weeks, but we would like to start calls again in teh last week of
February.
Does Wednesdays at 1930Z (11.30am US West coast, 2.30pm Boston, 2030
Eurotime) suit
On 2/25/09 7:46 PM, Garrett Smith wrote:
On Wed, Feb 25, 2009 at 8:27 AM, Charles McCathieNevile
cha...@opera.com wrote:
Hi folks,
unfortunately I have not been able to catch up with Doug (a combination of
both of us travelling and then I had a minor accident that put me out of
commission for
On 4/27/09 6:30 AM, Anne van Kesteren wrote:
Consider having two windows A and B where the session history of A
consists of A1 and in B it consists of B1 and B2. A1 and B2 are both
fully active. A1, B1, and B2 are all same-origin. Now everytime the
Storage object of A1 and B2 are updated B1 will
On 4/27/09 11:43 AM, Jonas Sicking wrote:
IIRC we do something similar with pages that have
listeners for 'beforeclose' listeners.
You mean 'beforeunload', and gecko does the same thing when page has
listeners for 'unload' .
-Olli
On 6/19/09 6:00 AM, timeless wrote:
On Fri, Jun 19, 2009 at 4:13 AM, Arun Ranganathana...@mozilla.com wrote:
Hixie, I think a Base64 representation of the file resource may be
sufficient, particularly for the image use case (which is how it is used
already). Can you flesh out why the new
On 6/30/09 1:44 PM, Ian Hickson wrote:
On Tue, 30 Jun 2009, Olli Pettay wrote:
File API should probably have some way to get only parts of the file.
getAsXXX(long long offset, long long length). Then uploading huge files
could be split and decoding video (or something like that) in JS might
On 6/30/09 4:07 PM, Thomas Broyer wrote:
On Tue, Jun 30, 2009 at 2:25 PM, Olli Pettay wrote:
On 6/30/09 1:44 PM, Ian Hickson wrote:
I'd rather just have an API that lets you split a File into a
sequenceFileData(where FileData is what File inherits from) of equally
sized chunks
On 8/6/09 9:31 PM, Jonas Sicking wrote:
On Wed, Aug 5, 2009 at 4:26 AM, Anne van Kesterenann...@opera.com wrote:
On Wed, 05 Aug 2009 10:04:28 +0200, Arun Ranganathana...@mozilla.com
wrote:
In the case of file read APIs, simply getting the data asynchronously is
more convenient than using
On 8/11/09 3:47 AM, Jonas Sicking wrote:
Today if you use XMLHttpRequest, you never have to worry if someone
else happen to be reading from the same URI as you, if we go with the
above API the same basically wouldn't be true for files.
Yes you do need to worry with XHR. If I call open/send, it
On 8/11/09 8:51 PM, Jonas Sicking wrote:
On Tue, Aug 11, 2009 at 1:56 AM, Olli Pettayolli.pet...@helsinki.fi wrote:
On 8/11/09 3:47 AM, Jonas Sicking wrote:
Today if you use XMLHttpRequest, you never have to worry if someone
else happen to be reading from the same URI as you, if we go with
On 8/11/09 3:47 AM, Jonas Sicking wrote:
It would mean that if you ever plan on reading from a File, you have
to be very careful never to pass that File to anyone. If you do, you
then have to slice the file before you read from it.
FileData object could have some property which tells what its
On 8/11/09 11:57 PM, Jonas Sicking wrote:
My concern isn't that there are ways of using it correctly, my concern
is that it's very easy to use incorrectly with bugs as a result.
How? Especially if we prevent more than one read at time. How is the
situation any worse than with XHR?
This
On 8/12/09 2:18 AM, Garrett Smith wrote:
On Tue, Aug 11, 2009 at 2:25 PM, Olli Pettayolli.pet...@helsinki.fi wrote:
On 8/11/09 11:57 PM, Jonas Sicking wrote:
My concern isn't that there are ways of using it correctly, my concern
is that it's very easy to use incorrectly with bugs as a
On 8/17/09 12:33 AM, Michael Nordman wrote:
Strictly speaking, I think the seperate 'Reader' class makes for a more
correct API. The two corners above would not conflict since each would
presumably be working with a distinct FileReader object. And the
seperate 'Reader' with event handlers seems
On 8/18/09 11:08 PM, Nikunj R. Mehta wrote:
Do we need asynchronous APIs if files are local and file system access
is fast?
Files that you select from file system aren't necessarily local and
the system access can be very slow in some cases.
I use sshfs all the time to mount remote systems to
On 8/24/09 7:21 PM, Marcin Hanclik wrote:
Thanks!
The issue is still there.
Sorry, but what issue? It is ok to use existing event interfaces for
other events than what is defined in the DOM spec.
Actually for mousewheel, wheel and textInput as I can see.
-Olli
On 9/24/09 4:51 PM, Deborah Dahl wrote:
Hello WebApps WG,
The Multimodal Interaction Working Group is working on specifications
that will support distributed applications that include inputs from
different modalities, such as speech, graphics and handwriting. We
believe there's some
On 10/2/09 7:31 AM, Darin Fisher wrote:
FileData::slice appears to be spec'd like so:
FileData slice(in long long offset, in long long length); // throws
FileException
This suggests that it may throw a file exception. I'm wondering if that
is a requirement? It seems that the rest of the
On 10/8/09 10:07 PM, Xiaomei Ji wrote:
One use case is to show a tooltip of the word's definition in your
accept-language when you mouse over the word in a page.
It needs to
1. convert the mouse position to character offset within a node (by
Document.caretRangeFromPoint()
On 10/14/09 3:40 AM, Garrett Smith wrote:
A blatant violation of US Patent: US20090225039.
Thanks for this information! I was a bit afraid of that Apple
might have done something evil like this.
[1] seems to be dated Sept. 10 2009.
-Olli
[1]
On 10/19/09 8:56 PM, João Eiras wrote:
to manipulate the objects you have on your device/OS.
Pan is scrolling for which browsers already fire events. The behavior
for the scroll event would need to change though, so it would be fired
before the event, and be cancelable.
Well, scroll event
On 1/28/10 9:34 PM, Jared Morse wrote:
Hi, I have a concern about the web storage event spec
(http://dev.w3.org/html5/webstorage/).
The spec states:
When the setItem(), removeItem(), and clear() methods are called on a
Storage object x that is associated with a local storage area, if the
, Jan 28, 2010 at 1:41 PM, Olli Pettay olli.pet...@helsinki.fi
mailto:olli.pet...@helsinki.fi wrote:
On 1/28/10 9:34 PM, Jared Morse wrote:
Hi, I have a concern about the web storage event spec
(http://dev.w3.org/html5/webstorage/).
The spec states:
When
On Thu, Jan 28, 2010 at 2:06 PM, Olli Pettay olli.pet...@helsinki.fi
mailto:olli.pet...@helsinki.fi wrote:
On 1/28/10 11:57 PM, Jared Morse wrote:
Even though it occurs on the same document, doesn't mean loosely
coupled
code can't benefit from it.
Imagine if each
On 1/27/10 9:39 AM, Zhiheng Wang wrote:
Folks,
Thanks to the much feedback from various developers, the WebTiming
specs has undergone some
major revision. Timing info has now been extended to page elements and a
couple more interesting timing
data points are added. The draft is up on
On 2/2/10 11:09 PM, Gregg Tavares wrote:
I'm not sure if this is the correct place for this but:
Has there been any discussion of adding an element.onresize event?
The issue that has come up is the canvas tag, in 2d or 3d, when the canvas
changes its displayed size, a webapp might want to
On 2/2/10 11:56 PM, Jonas Sicking wrote:
The problem with this is one of performance.
And the problem is also how to specify it so that
resize events loops aren't possible (or at least not easy to cause).
What if resize event listener causes a new resize ...
-Olli
Btw, discussion about DOM
Hi all,
some random comments about
http://dev.w3.org/2006/webapi/WebNotifications/publish/
(I didn't know that the draft existed until the link was mentioned
in an email to @whatwg mailing list :/ )
NotificationCenter is a bit strange. Why do we need
a separate interface for this?
I'd rather
On 2/3/10 8:33 PM, John Gregg wrote:
I will make this more specific in the draft: create[HTML]Notification
should not load the necessary resources until it is about to be
displayed (in case of a queue). Once it is at the top of the queue, it
should:
- load its resources as if opening a new
On 2/3/10 8:55 PM, Jeremy Orlow wrote:
Agreed. Having a shared worker that doesn't need to worry about races
with shutting down windows seems like a big win.
Olli, do you foresee any problems with allowing access from workers?
In a multiscreen environment worker can't define which screen to
Hi,
I wonder why send() needs to buffer anything after the connection is
closed. bufferedAmount is defined: If the connection is closed, this
attribute's value will only increase with each call to the send() method
(the number does not reset to zero once the connection closes)
Why not clear
On 2/19/10 12:59 AM, Ian Hickson wrote:
On Thu, 18 Feb 2010, Olli Pettay wrote:
I wonder why send() needs to buffer anything after the connection is
closed. bufferedAmount is defined: If the connection is closed, this
attribute's value will only increase with each call to the send() method
On 2/20/10 11:40 PM, Ian Hickson wrote:
On Fri, 19 Feb 2010, Olli Pettay wrote:
On 2/19/10 5:09 AM, Ian Hickson wrote:
On Fri, 19 Feb 2010, Wellington Fernando de Macedo wrote:
Frame boundary bits are taken account in bufferedAmount?
This is surprising. Very surprising.
Web Socket API
Hi Mike,
FYI,
I wrote a wip patch for Gecko.
https://bugzilla.mozilla.org/show_bug.cgi?id=559092
Test builds will be here:
https://build.mozilla.org/tryserver-builds/opet...@mozilla.com-xhr_priority/
-Olli
On 4/13/10 8:36 PM, Mike Belshe wrote:
On Tue, Apr 13, 2010 at 9:36 AM, Olli Pettay
No comments to this?
I wish the API will be changed and the awkward CloseEvent
interface will be removed.
-Olli
On 3/18/10 12:15 AM, Olli Pettay wrote:
Hi all,
I was wondering why to have .wasClean in
close event. Is there really need for adding
yet another event interface. Especially
On 4/21/10 1:51 AM, Jian Li wrote:
According to the spec, we will dispatch a progress event for a read
method. But per the Progress Events 1.0 spec, the attributes loaded
and total are defined as unsigned long.
interface ProgressEvent : events::Event {
...
readonly
On 4/21/10 1:51 AM, Jian Li wrote:
According to the spec, we will dispatch a progress event for a read
method. But per the Progress Events 1.0 spec, the attributes loaded
and total are defined as unsigned long.
interface ProgressEvent : events::Event {
...
readonly
On 5/11/10 11:43 AM, J Ross Nicoll wrote:
Looking at http://www.w3.org/TR/2009/WD-FileAPI-20091117/#dfn-file
Note, discussion about FileAPI should happen in WebApps WG mailing list.
There doesn't appear to be anyway of retrieving creation date,
modification date or size of the file.
You
XHR2 related discussion happens in WebApps WG.
Forwarding...
Original Message
Subject: [whatwg] what happened to sendAsBinary?
Date: Wed, 30 Jun 2010 13:27:09 +0300
From: Toni Ruottu toni.ruo...@iki.fi
To: wha...@whatwg.org
hello
We are trying to code an application that
On 09/15/2010 08:55 PM, Web Applications Working Group Issue Tracker wrote:
ISSUE-126 (isTrusted): Consider changing 'trusted' to 'isTrusted' [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/126
Raised by: Doug Schepers
On product: DOM3 Events
Simon
On 10/20/2010 12:11 PM, Scott Wilson wrote:
I've just had a look at this:
https://apps.mozillalabs.com/
In some respects this is very much what we are aiming for (apps using HTML+JS+CSS) however it
proposes a new proprietary app manifest format for Widgets that is almost
identical to PC,
On 10/21/2010 09:43 AM, Maciej Stachowiak wrote:
On Oct 20, 2010, at 9:41 PM, Adam Barth wrote:
On Wed, Oct 20, 2010 at 7:14 AM, Stewart Brodie
stewart.bro...@antplc.com wrote:
Henri Sivonenhsivo...@iki.fi wrote:
When WebKit or Firefox trunk create an HTML script element node
via
Hi all,
Workers seem to use NavigatorOnLine, but it is not specified
whether online/offline events should be dispatched.
I think they should be, since otherwise tracking the changes to
.onLine is hard.
-Olli
On 10/30/2010 09:34 AM, Jonas Sicking wrote:
On Fri, Oct 29, 2010 at 10:43 PM, Boris Zbarskybzbar...@mit.edu wrote:
On 10/28/10 11:29 PM, Jonas Sicking wrote:
Personally I like the proposed responseType solution.
The one where you pick one up front and it throws if you ask for something
On 11/01/2010 08:57 PM, Chris Marrin wrote:
On Nov 1, 2010, at 12:47 PM, Olli Pettay wrote:
On 10/30/2010 09:34 AM, Jonas Sicking wrote:
On Fri, Oct 29, 2010 at 10:43 PM, Boris Zbarskybzbar...@mit.edu
wrote:
On 10/28/10 11:29 PM, Jonas Sicking wrote:
Personally I like the proposed
On 12/14/2010 01:24 PM, Dimitri Glazkov wrote:
Dear all,
Looking at the use cases and the problems the current XBL2 spec is
trying address, I think it might be a good idea to rename it into
something that is less legacy-bound? Hixie already cleverly disguised
the X as [X]engamous in the latest
On 12/16/2010 11:52 AM, Tab Atkins Jr. wrote:
On Thu, Dec 16, 2010 at 10:40 AM, Boris Zbarskybzbar...@mit.edu wrote:
On 12/15/10 11:29 AM, Dimitri Glazkov wrote:
That seems like an implementation detail. Metadata can be shared and
cloned as needed, just like styles in CSS.
Sort of. It
On 10/22/2010 10:09 PM, Jonas Sicking wrote:
On Fri, Oct 22, 2010 at 11:15 AM, Erik Arvidssona...@chromium.org wrote:
On Oct 22, 2010 2:00 AM, Anne van Kesterenann...@opera.com wrote:
Yeah, I don't mind moving these features to libraries. Anyone implemented
them apart from Opera?
Neither
Hi,
takeChildNodes() could be useful in some cases, but
it is already easy to achieve the same without any loops.
Something like:
var r = document.createRange();
r.selectNodeContents(originalParent);
destinationParent.appendChild(r.extractContents());
So since it is already easy to move a group
Hi all,
the current File API: Directories and System seems to use
callbacks and not events, yet other
File APIs (the ones for read and write) use events.
That is quite major inconsistency in the APIs.
IIRC there was already some discussion about which approach to use
when the API for read was
On 02/12/2011 01:08 AM, Eric Uhrhane wrote:
On Fri, Feb 11, 2011 at 7:43 AM, Olli Pettayolli.pet...@helsinki.fi wrote:
Hi all,
the current File API: Directories and System seems to use
callbacks and not events, yet other
File APIs (the ones for read and write) use events.
That is quite major
On 03/02/2011 09:02 AM, Ben Dilts wrote:
Why is there no mechanism for paging results, a la SQL's limit? If I
want entries in positions 140-159 from an index, I have to call
continue() on a cursor 139 times, which in turn unserializes 139 objects
from my store that I don't care about, which in
On 03/09/2011 04:14 PM, Arthur Barstow wrote:
Ian, Leigh, Dimitri, All,
On March 11, the agenda of the so-called Hypertext Coordination Group
[HCG] will include XBL [XBL] to continue related discussions they had
during their Feb 11 call [Feb-11-Mins]. I wasn't present at that call
but based on
On 11/12/2009 05:24 PM, Anne van Kesteren wrote:
On Wed, 11 Nov 2009 00:03:07 +0100, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Nov 10, 2009 at 10:17 AM, Anne van Kesteren ann...@opera.com
wrote:
Anyway, do you have opinions on the synchronous case? Do you agree we
should use TIMEOUT_ERR
On 03/17/2011 08:40 PM, Glenn Maynard wrote:
From https://bugzilla.mozilla.org/show_bug.cgi?id=637002:
If you leave this as invalid, would it at least be possible (or even necessary)
to fire the progress event one last time (e.g. right when finished sending all
bytes without waiting for the
On 03/17/2011 09:09 PM, Olli Pettay wrote:
On 03/17/2011 08:40 PM, Glenn Maynard wrote:
From https://bugzilla.mozilla.org/show_bug.cgi?id=637002:
If you leave this as invalid, would it at least be possible (or even
necessary)
to fire the progress event one last time (e.g. right when finished
On 03/20/2011 01:36 AM, Tony Gentilcore wrote:
Hi all,
Back in October I proposed the SearchBox API to the whatwg [1]. It
enables instant style interaction between the user agent's search
box and the default search provider's results page.
When I tried instant search on Chrome, it did
On 04/12/2011 05:33 PM, Eric Uhrhane wrote:
On Tue, Apr 12, 2011 at 3:38 PM, Kyle Hueym...@kylehuey.com wrote:
Hello All,
In the current FileAPI Writer spec a BlobBuilder can be used to build a
series of blobs like so:
var bb = BlobBuilder();
bb.append(foo);
var foo = bb.getBlob();
On 04/26/2011 12:22 AM, Ojan Vafai wrote:
On Mon, Apr 25, 2011 at 11:31 AM, Jonas Sicking jo...@sicking.cc wrote:
First off is document.createTreeWalker and
document.createNodeIterator. They have the same signature which
currently is:
document.createX(root, whatToShow, filter,
HI Rafael,
few random comments, or mainly just random questions :)
On 04/23/2011 03:35 AM, Rafael Weinstein wrote:
Myself and a few other chromium folks have been working on a design
for a formalized separation between View and Model in the browser,
with needs of web applications being the
On 04/27/2011 09:13 PM, Erik Arvidsson wrote:
On Wed, Apr 27, 2011 at 08:33, Olli Pettayolli.pet...@helsinki.fi wrote:
Not sure why this had some relation with XBL. Unless you are
planning to put the template based DOM nodes to anonymous DOM.
The relation to XBL is that XBL has a template
On 04/28/2011 12:02 PM, Maciej Stachowiak wrote:
On Apr 27, 2011, at 6:46 PM, Rafael Weinstein wrote:
What do you think?
- Is this something you'd like to be implemented in the
browsers,
Yes.
and if yes, why? What would be the reasons to not just use
script libraries (like your
On 04/28/2011 04:46 AM, Rafael Weinstein wrote:
Would be good to know what are the use cases you had in mind.
I'm never sure if I'm using the term use case correctly =-).
Our primary motivator is the needs of web applications,
And what are those needs? It is hard to judge the proposal
if
On 04/29/2011 04:11 AM, Garrett Smith wrote:
On 4/28/11, Olli Pettayolli.pet...@helsinki.fi wrote:
On 04/28/2011 04:46 AM, Rafael Weinstein wrote:
Would be good to know what are the use cases you had in mind.
I'm never sure if I'm using the term use case correctly =-).
Our primary
On 05/03/2011 02:38 PM, Arthur Barstow wrote:
Hi All,
Pardon the interruption here to digress a bit to look at Rafael's
proposal from the process perspective ...
[Charter] defines WebApps' scope and explicit deliverables. Depending on
how the proposal is viewed, (perhaps) at least part of it
On 05/09/2011 11:58 AM, Hironori Bono (坊野 博典) wrote:
Greetings,
I'm Hironori Bono, a software engineer for Google Chrome.
We recently received requests from web-application developers (and
extension developers) that they would like to use the spellchecker
Quite different targets.
integrated
On 05/10/2011 01:44 AM, Aryeh Gregor wrote:
On Mon, May 9, 2011 at 3:49 PM, Boris Zbarskybzbar...@mit.edu wrote:
This does mean firing tens of thousands of events during load on some pages
(e.g. wikipedia article edit pages) Maybe that's not a big deal.
If that's too many events,
On 05/10/2011 08:33 PM, Aryeh Gregor wrote:
On Tue, May 10, 2011 at 7:49 AM, Olli Pettayolli.pet...@helsinki.fi wrote:
Just a quick test on Nokia N900 (which is already a bit old mobile
phone) using a recent browser:
dispatching 1 events to a deep (depth 100) DOM (without
listeners for the
On 05/10/2011 08:33 PM, Adam Shannon wrote:
On Tue, May 10, 2011 at 06:49, Olli Pettayolli.pet...@helsinki.fi wrote:
On 05/10/2011 01:44 AM, Aryeh Gregor wrote:
On Mon, May 9, 2011 at 3:49 PM, Boris Zbarskybzbar...@mit.eduwrote:
This does mean firing tens of thousands of events during
On 05/12/2011 01:29 AM, Aryeh Gregor wrote:
2011/5/11 timelesstimel...@gmail.com:
With this model, i'd want the UA to provide instances for words which
are misspelled according to its standard dictionary but which are in
its user's custom dictionary. The web page can try to make
suggestions,
On 05/13/2011 11:39 PM, Jonas Sicking wrote:
On Fri, May 13, 2011 at 1:21 PM, Boris Zbarskybzbar...@mit.edu wrote:
On 5/13/11 4:07 PM, Jonas Sicking wrote:
It *does* however call for a readystatechange event to be fired in
response to the call to .open. Even if the request being started is a
On 01/31/2011 11:02 AM, Ryosuke Niwa wrote:
On Tue, Jan 25, 2011 at 9:26 PM, Hallvord R. M. Steen
hallv...@opera.com mailto:hallv...@opera.com wrote:
On Thu, 06 Jan 2011 07:41:01 +0900, Ryosuke Niwa rn...@webkit.org
mailto:rn...@webkit.org wrote:
In an editable context, the
On 06/17/2011 01:21 AM, Vincent Scheib wrote:
- 2 new methods on an element to enter and exit mouse lock. Two
callbacks on the entering call provide notification of success or failure.
- Mousemove event gains .deltaX .deltaY members, always valid, not just
during mouse lock.
I don't understand
On 06/20/2011 10:18 PM, Jonas Sicking wrote:
On Mon, Jun 20, 2011 at 11:17 AM, Adam Barthw...@adambarth.com wrote:
On Mon, Jun 20, 2011 at 10:48 AM, Tab Atkins Jr.jackalm...@gmail.com wrote:
On Mon, Jun 20, 2011 at 10:18 AM, Adam Barthw...@adambarth.com wrote:
So it sounds like we don't
On 06/21/2011 12:25 AM, Tab Atkins Jr. wrote:
On Mon, Jun 20, 2011 at 1:19 PM, Olli Pettayolli.pet...@helsinki.fi wrote:
On 06/20/2011 10:18 PM, Jonas Sicking wrote:
On Mon, Jun 20, 2011 at 11:17 AM, Adam Barthw...@adambarth.comwrote:
On Mon, Jun 20, 2011 at 10:48 AM, Tab Atkins
On 06/21/2011 01:08 AM, Tab Atkins Jr. wrote:
On Mon, Jun 20, 2011 at 3:03 PM, Olli Pettayolli.pet...@helsinki.fi wrote:
On 06/21/2011 12:25 AM, Tab Atkins Jr. wrote:
The use-case is non-fullscreen games and similar, where you'd prefer
to lock the mouse as soon as the user clicks into the
On 06/22/2011 06:17 PM, Tab Atkins Jr. wrote:
On Wed, Jun 22, 2011 at 8:02 AM, Ryosuke Niwarn...@webkit.org wrote:
On Mon, Jun 20, 2011 at 10:48 AM, Tab Atkins Jr.jackalm...@gmail.com
wrote:
2. During a user-initiated click, you can lock the mouse to the target
or an ancestor without a
On 06/28/2011 03:36 PM, Anne van Kesteren wrote:
On Tue, 28 Jun 2011 13:30:09 +0200, Olli Pettay
olli.pet...@helsinki.fi wrote:
There is now a patch for Gecko to implement a variant of this
proposal https://bugzilla.mozilla.org/show_bug.cgi?id=641821
The patch adds the following methods
On 06/30/2011 12:54 AM, Rafael Weinstein wrote:
On Wed, Jun 29, 2011 at 7:13 AM, Aryeh Gregorsimetrical+...@gmail.com wrote:
On Tue, Jun 28, 2011 at 5:24 PM, Jonas Sickingjo...@sicking.cc wrote:
This new proposal solves both these by making all the modifications
first, then firing all the
On 06/30/2011 09:36 PM, David Flanagan wrote:
[Callback, NoInterfaceObject]
interface MutationCallback
{
// aNode is the node to which the listener was added.
// aChangeTarget is the node in which the mutation was made.
void handleMutation(in Node aNode, in Node aChangeTarget);
};
Won't the
On 07/02/2011 12:59 AM, David Flanagan wrote:
On 7/1/11 2:06 PM, Rafael Weinstein wrote:
On Fri, Jul 1, 2011 at 12:43 PM, David Flanagandflana...@mozilla.com
wrote:
As I see it, the test of sufficiency of set of mutation event is if
you can
use them to mirror a document tree. And in my case
On 07/02/2011 09:27 PM, Dave Raggett wrote:
Olli Pettay
Tue, 28 Jun 2011 04:32:14 -0700
These are *not* DOM-Event listeners. No DOM Events are created, there
are no capture phases or bubbling phases. Instead you register a
listener on the node you are interested in being notified about
On 07/02/2011 08:46 PM, John J. Barton wrote:
Olli Pettay
Tue, 28 Jun 2011 04:32:14 -0700
These are *not* DOM-Event listeners. No DOM Events are created, there
are no capture phases or bubbling phases. Instead you register a
listener on the node you are interested in being notified about
On 07/04/2011 07:23 PM, John J. Barton wrote:
On 7/3/2011 1:23 PM, Boris Zbarsky wrote:
On 7/3/11 2:43 PM, John J. Barton wrote:
I'm not sure what you're asking... The whole point of the proposed
model is that if someone tries to do a mutation the mutation _will_
happen and will complete.
On 07/04/2011 07:28 PM, Ojan Vafai wrote:
Apologies in advance if my comment makes no sense. This is a long
thread, I tried to digest it all. :)
On Sat, Jul 2, 2011 at 7:07 AM, Boris Zbarsky bzbar...@mit.edu
mailto:bzbar...@mit.edu wrote:
That may be ok, if the use cases that incur this
1 - 100 of 241 matches
Mail list logo
