On 14.09.2010 18:52, Darin Fisher wrote:
...
That's a good point. Note, resolving the Location header is only one of the
issues. Another is knowing what HTTP method to use in response to a
redirect.
...
Always the same as for the original request, except for 303 :-).
On 9/15/10 12:13 AM, Julian Reschke wrote:
On 14.09.2010 18:52, Darin Fisher wrote:
...
That's a good point. Note, resolving the Location header is only one
of the
issues. Another is knowing what HTTP method to use in response to a
redirect.
...
Always the same as for the original request,
On 15.09.2010 09:58, Boris Zbarsky wrote:
On 9/15/10 12:13 AM, Julian Reschke wrote:
On 14.09.2010 18:52, Darin Fisher wrote:
...
That's a good point. Note, resolving the Location header is only one
of the
issues. Another is knowing what HTTP method to use in response to a
redirect.
...
On 9/15/10 1:10 AM, Julian Reschke wrote:
Yes. However, I was only 50% joking. Are we sure that XHR should behave
the same?
Why should it behave differently from every single other HTTP request
the browser makes? That seems like adding complexity for the sake of
complexity...
-Boris
On 15.09.2010 10:16, Boris Zbarsky wrote:
On 9/15/10 1:10 AM, Julian Reschke wrote:
Yes. However, I was only 50% joking. Are we sure that XHR should behave
the same?
Why should it behave differently from every single other HTTP request
the browser makes? That seems like adding complexity for
On 9/15/10 1:37 AM, Julian Reschke wrote:
What browsers do today is a bug per spec.
Well, yes, but they implemented it that way as a specific workaround for
broken servers, no?
Use cases for XHR are not identical to surfing web pages. There are
protocols/implementations that expect method
On 9/15/10 2:40 AM, Julian Reschke wrote:
Well, yes, but they implemented it that way as a specific workaround for
broken servers, no?
I'm not sure about that.
Hmm, fair. I just looked up the history of this code in Gecko, and the
best I can give you is
On 9/15/10 2:47 AM, Boris Zbarsky wrote:
So it's possible that the original behavior was just an oversight that
then got copied. Someone with access to a browser version control system
from before 1998 would need to look to make sure...
It's also possible that no UA implementor was willing to
On 15.09.2010 11:56, Boris Zbarsky wrote:
On 9/15/10 2:47 AM, Boris Zbarsky wrote:
So it's possible that the original behavior was just an oversight that
then got copied. Someone with access to a browser version control system
from before 1998 would need to look to make sure...
It's also
There will be no widget call on September 16; the next call is
September 23.
All of the open Issues and Actions for widgets are available at the
following
http://www.w3.org/2008/webapps/track/products/8
The higher priority Actions/ToDos are:
= Packaging and Configuration spec: need
FYI, Nathan and others discussed Nathan's e-mail on the device-apis list:
http://lists.w3.org/Archives/Public/public-device-apis/2010Sep/0034.html
On 9/3/10 1:52 PM, ext Nathan wrote:
Hi All,
Simply wondering why WARP, Widgets Updates and Digital Signatures aren't
used to deploy js
I think it's clear what IDBCursor does when created from
IDBObjectStore.openCursor or IDBIndex.openObjectCursor: it modifies the
objectStore's value and updates all indexes (or does nothing and returns an
error if all of that can't be done while satisfying the constraints).
But what about
ISSUE-123 (feature strings): Rationale for feature strings [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/123
Raised by: Doug Schepers
On product: DOM3 Events
Simon Pieters
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html:
[[
What's the use case for extended feature
ISSUE-124 (reword examples): Remove RFC2119 keywords from examples [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/124
Raised by: Doug Schepers
On product: DOM3 Events
Simon Pieters
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html:
[[
RFC2119 keywords in examples is
ISSUE-125 (DOM Views): Consider dropping DOM Views reference for HTML5
defaultView [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/125
Raised by: Doug Schepers
On product: DOM3 Events
Simon Pieters
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html:
[[
{
The
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 Pieters
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html:
[[
Gecko has a property called
ISSUE-127 (cancelBubble / srcElement): Consider adding cancelBubble and
srcElement [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/127
Raised by: Doug Schepers
On product: DOM3 Events
Simon Pieters
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html:
[[
Looking at [6],
ISSUE-128 (preventDefault): Define preventDefault to account for
pre-propagation default actions [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/128
Raised by: Doug Schepers
On product: DOM3 Events
Simon Pieters
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html:
[[
ISSUE-129 (event constructors): Revist event constructors [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/129
Raised by: Doug Schepers
On product: DOM3 Events
Simon Pieters
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html:
[[
An idea for creating events is to support
ISSUE-130 (Web IDL): Consider using Web IDL for the IDL fragments [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/130
Raised by: Doug Schepers
On product: DOM3 Events
Simon Pieters
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html:
[[
I think this specification should
ISSUE-131 (defaultView load ): Define load event to fire on defaultView [DOM3
Events]
http://www.w3.org/2008/webapps/track/issues/131
Raised by: Doug Schepers
On product: DOM3 Events
Simon Pieters
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0125.html:
[[
{
Note: for legacy
ISSUE-132 (event.returnValue): Consider adding event.returnValue [DOM3 Events]
http://www.w3.org/2008/webapps/track/issues/132
Raised by: Doug Schepers
On product: DOM3 Events
Hallvord R. M. Steen
http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0142.html:
[[
IE lets you prevent the
Hi, Folks-
I appreciate all the comments on DOM3 Events so far. I'm filing each of
them in Tracker, though it may take me a few days to file a bug;
however, I am reading all of them, and will get around to filing them all.
Currently, the WebApps Tracker sends the emails for each filed issue
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 9/7/10 10:08 PM, Darin Fisher wrote:
On Tue, Sep 7, 2010 at 5:23 PM, Kenneth Russell k...@google.com
mailto:k...@google.com wrote:
On Tue, Sep 7, 2010 at 4:19 PM, Nathan nat...@webr3.org
mailto:nat...@webr3.org wrote:
Jian Li wrote:
Hi,
Several specs, like
25 matches
Mail list logo
