On Mon, Jun 2, 2014 at 6:59 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, May 29, 2014 at 4:25 PM, Takeshi Yoshino tyosh...@google.com
wrote:
http://fetch.spec.whatwg.org/#dom-request
Add steps to set client and context?
That happens as part of the restricted copy. However, that
For XHR.send(), we've finally chosen to accept only ArrayBufferView.
http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0141.html
Do we want to do the same for FetchBody body of RequestInit?
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25970
Bug ID: 25970
Summary: [WebSocket API] What Step 1 means is unclear. And
typo report
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
On Wed, Jun 4, 2014 at 8:13 AM, Takeshi Yoshino tyosh...@google.com wrote:
On Mon, Jun 2, 2014 at 6:59 PM, Anne van Kesteren ann...@annevk.nl wrote:
That's an internal algorithm never directly used. You can only get
there from http://fetch.spec.whatwg.org/#concept-fetch and that can
only be
On Wed, Jun 4, 2014 at 8:30 AM, Takeshi Yoshino tyosh...@google.com wrote:
For XHR.send(), we've finally chosen to accept only ArrayBufferView.
http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0141.html
Do we want to do the same for FetchBody body of RequestInit?
What I really
On Tue, Jun 3, 2014 at 9:00 PM, Jonas Sicking jo...@sicking.cc wrote:
One thing we should keep in mind is if we actually need to support
100% of all the crazyness that servers do. And especially if we need
to support it in a particularly convenient way.
Yes, that is
On Tue, Jun 3, 2014 at 7:20 PM, Oda, Terri terri@intel.com wrote:
Perhaps it would make sense to also require explicit allowing of imports via
CSP? Scripts are allowed when no CSP is provided for historical
compatibility so you'd need to make sure that imports fell under a separate
On Wed, Jun 4, 2014 at 9:49 AM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Jun 4, 2014 at 12:31 AM, Anne van Kesteren ann...@annevk.nl wrote:
Does ES define the order of { x: a, y: b } btw?
I believe so, but someone would need to check. Either way I think
browsers effectively are forced to
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18701
Art Barstow art.bars...@nokia.com changed:
What|Removed |Added
Status|NEW |RESOLVED
According to the spec, the send() method of XmlHttpRequest objects
enable an internal 'send()' flag showing that the request has been
done, and not allowing to do several requests on the same XHR object,
although the current API with an open() method leads to think that's
possible. Due to this, I
On Wed, Jun 4, 2014 at 2:45 PM, pira...@gmail.com pira...@gmail.com wrote:
According to the spec, the send() method of XmlHttpRequest objects
enable an internal 'send()' flag showing that the request has been
done, and not allowing to do several requests on the same XHR object,
although the
The send() flag is only set as long as the fetch is ongoing. Once the
fetch has finished, it is no longer set. So this is already possible.
I did some tests some months ago and I was not be able to achieve it,
nor found any info or examples on Internet about if it's or it's not
possible.
So,
On Wed, Jun 4, 2014 at 3:05 PM, pira...@gmail.com pira...@gmail.com wrote:
The send() flag is only set as long as the fetch is ongoing. Once the
fetch has finished, it is no longer set. So this is already possible.
I did some tests some months ago and I was not be able to achieve it,
nor
You need to invoke open() to set the object in the proper state.
Ok, good trick (didn't know it, thanks :-) ), but I was asking about
with just one call to .open(), being able to call several times to
.send(). That's why I did the reference to KeepAlive header.
--
Si quieres viajar alrededor
Hi All,
Yesterday I received a request to hold a spec-specific distributed
meeting, with the expectation the meeting would use the #webapps IRC
channel as well as the Consortium's voice conference system. Although I
fully support this proposal, and encourage all Editors and active
Hi WebApps,
There will be a conference call on June 6th at 08:00 (8am) San Francisco time
(PST) to discuss the recent editing topics contentEditable=minimal and
CommandEvent[1]. We will be on #webapps with Zakim and will send minutes to
this list. The pin and further details will be sent
The 2 June 2014 Editor’s Draft of the File API solves some bugs and technical
issues with Blob URLs. Review is encouraged, with a view towards a LCWD
publication:
http://dev.w3.org/2006/webapi/FileAPI/
In particular:
1. It nails down syntax differences between user agents on Blob URLs.
2. It
There has been some conversation about browser UI for Commands with
ContentEdtiable=minimal. Some people seem to believe that UI should not be
displayed because it may not be relevant. One way to solve this is to have an
event that would allow script to tell the browser what is relevant. Today,
On Wed, Jun 4, 2014 at 2:46 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Wed, Jun 4, 2014 at 9:49 AM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Jun 4, 2014 at 12:31 AM, Anne van Kesteren ann...@annevk.nl wrote:
Does ES define the order of { x: a, y: b } btw?
I believe so, but someone
On 6/4/14 11:42 AM, Ben Peters wrote:
There will be a conference call on June 6th at 08:00 (8am) San
Francisco time (PST) to discuss the recent editing topics
contentEditable=minimal and CommandEvent[1]. We will be on #webapps
with Zakim and will send minutes to this list. The pin and further
DOM L3 does require implementations to fire composition event for dead-key
combinations, so insofar as the (Alt-`) combo results in a dead key for
accent-grave (and other dead key combos mentioned below), the composition
events should (or are supposed to) fire as a result.
-Original
21 matches
Mail list logo
