On Tue, 12 Jun 2012, Simon Pieters wrote:
The potentially CORS-enabled fetch algorithm ignores the state of the
crossorigin attribute when the URL is same-origin. Maybe the sync
loading logic needs to align with that behavior.
The problem is that it doesn't actually entirely ignore it, in
On Tue, 12 Jun 2012 20:38:08 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/12/12 4:47 AM, Simon Pieters wrote:
The potentially CORS-enabled fetch algorithm ignores the state of the
crossorigin attribute when the URL is same-origin.
Hmm. On the face of it, this seems like a bug when open
On 6/13/12 4:55 AM, Simon Pieters wrote:
If it redirects, it switches to CORS. However, there are some bugs in
the spec... I just filed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17478 now.
Can we push this whole algorithm down into the CORS spec? It looks like
at this point
On Wed, 13 Jun 2012 18:09:22 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/13/12 4:55 AM, Simon Pieters wrote:
If it redirects, it switches to CORS. However, there are some bugs in
the spec... I just filed
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17478 now.
Can we push this whole
On Wed, 13 Jun 2012, Simon Pieters wrote:
On Wed, 13 Jun 2012 18:09:22 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/13/12 4:55 AM, Simon Pieters wrote:
If it redirects, it switches to CORS. However, there are some bugs
in the spec... I just filed
On Mon, 11 Jun 2012 22:53:30 +0200, wha...@whatwg.org wrote:
Author: ianh
Date: 2012-06-11 13:53:26 -0700 (Mon, 11 Jun 2012)
New Revision: 7128
Modified:
complete.html
index
source
Log:
[giow] (2) Try to define img synchronous loading.
Affected topics: HTML
Modified: source
On 6/12/12 4:47 AM, Simon Pieters wrote:
The potentially CORS-enabled fetch algorithm ignores the state of the
crossorigin attribute when the URL is same-origin.
Hmm. On the face of it, this seems like a bug when open redirectors are
involved... Is this what UAs implement in practice?
