Anne,
The commit on the W3C CORS spec in May 2012 [1] has moved various useful
texts explaining decisions made and reasons to the CORS FAQ wiki page [2].
The Fetch spec [3] inherited the CORS concepts/algorithms but seems didn't
inherit stuff in the FAQ.
Could you please try to guide readers of
I asked this question because I spent much time to understand the reason
why credentials are omitted for preflight requests. But it seems the
current Fetch spec has a different algorithm than the W3C CORS spec.
The commit
On Fri, Aug 15, 2014 at 1:37 AM, Robert Bindar robertbin...@gmail.com wrote:
We can not say accurately if the default will always be false because
the platform may or may not support the behavior, or it might be overridden
by a user defined setting.
Well, if we introduce new dictionary members
On Fri, Aug 15, 2014 at 1:54 AM, Michael Henretty
michael.henre...@gmail.com wrote:
On this note, it would be useful if content could query the UA for the
default behaviors of any notifications it would send. Also, it would be
nice to know which of these behaviors could be overridden by the
于 2014/8/14 21:23, Nils Dagsson Moskopp 写道:
duanyao duan...@ustc.edu writes:
On 07/28/2014 22:08, Gordon P. Hemsley wrote:
On 07/28/2014 08:01 AM, duanyao wrote:
On 07/28/2014 06:34, Gordon P. Hemsley wrote:
Sorry for the delay in responding. Your message fell through the
cracks in my
On Fri, Aug 15, 2014 at 9:01 AM, Takeshi Yoshino tyosh...@google.com wrote:
I asked this question because I spent much time to understand the reason why
credentials are omitted for preflight requests.
I think that was because it was a new type of request and we generally
consider sending
On Fri, Aug 15, 2014 at 7:09 PM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Aug 15, 2014 at 9:01 AM, Takeshi Yoshino tyosh...@google.com
wrote:
I asked this question because I spent much time to understand the reason
why
credentials are omitted for preflight requests.
I think that
On Fri, Aug 15, 2014 at 7:12 PM, Takeshi Yoshino tyosh...@google.com
wrote:
On Fri, Aug 15, 2014 at 7:09 PM, Anne van Kesteren ann...@annevk.nl
wrote:
On Fri, Aug 15, 2014 at 9:01 AM, Takeshi Yoshino tyosh...@google.com
wrote:
I asked this question because I spent much time to understand
Hi,
in order to prevent whatever default action Notification's click event has
(for example focus the tab which initiated the Notification), the click event
should be cancelable so that .preventDefault() can be called.
Some background
On Thu, 14 Aug 2014, at 11:00, Jonas Sicking wrote:
I am however more worried about that only having a request() and a
release() function means that pages that contain multiple independent
subsystems will have to make sure that they don't stomp on each
other's locks. Simply counting request()
On Aug 15, 2014 1:57 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Aug 15, 2014 at 1:37 AM, Robert Bindar robertbin...@gmail.com
wrote:
We can not say accurately if the default will always be false because
the platform may or may not support the behavior, or it might be
overridden
Hey,
Thanks for writing this up!
So to the extent we are simply exposing http/2 semantics, this spec seems
pretty clear. Two questions that I have that aren't answered by the http/2
spec:
- What do we expect the browser to do with priorities set cross domain. Eg,
if I express that a.com/foo.js
On Mon, 11 Aug 2014, Ilya Grigorik wrote:
On Mon, Aug 11, 2014 at 12:57 PM, Ian Hickson i...@hixie.ch wrote:
I hope to be able to post more concrete proposals soon, it's currently
blocked on my understanding how I should be integrating HTML with ES6.
Any bugs or threads that I can
On Fri, Aug 15, 2014 at 8:38 AM, Ben Maurer ben.mau...@gmail.com wrote:
Hey,
Thanks for writing this up!
So to the extent we are simply exposing http/2 semantics, this spec seems
pretty clear. Two questions that I have that aren't answered by the http/2
spec:
- What do we expect the
On Thu, 14 Aug 2014, Ilya Grigorik wrote:
Trying to hash out some ideas for how to connect Fetch and the new
transport capabilities of HTTP/2.
It would be great to get a set of use cases describing what your proposal
is addressing, since that would more easily let people evaluate whether
Some cases I can think of off the top of my head:
- A website has a page where media is the primary content. It would like to
make sure that media is downloaded before JS (example: you go to
flicker.com/my-image, the browser should probably prioiritize that image
over a pice of javascript that is
Hi All,
Right now the meta referrer spec has two separate features:
You can specify a origin policy which enables sending just the
origin whenever a referrer is sent.
You can also specify always in order to override UA policies like
don't send referrer when navigating from https to http sites.
On Fri, Aug 15, 2014 at 9:26 AM, Ian Hickson i...@hixie.ch wrote:
Two high-level cases:
(a) optimizing load sequence of page that's currently being loaded
(b) optimizing page load of a (potential) future navigation
For (a), we need to expose preconnect and preload, such that the
On Fri, 15 Aug 2014, Ilya Grigorik wrote:
- link href='https://fonts.googleapis.com/css?family=Open+Sans'
rel='stylesheet'
- above stylesheet is dynamic and returns a pointer to a UA optimized
font file that lives on https://fonts.gstatic.com
Ah, yeah, that's an excellent example. Thanks.
On Fri, Aug 15, 2014 at 6:14 AM, Mounir Lamouri mou...@lamouri.fr wrote:
On Thu, 14 Aug 2014, at 11:00, Jonas Sicking wrote:
I am however more worried about that only having a request() and a
release() function means that pages that contain multiple independent
subsystems will have to make
20 matches
Mail list logo
