[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Difference in CORS implementation between Firefox and Chrome




On 03/08/11 03:21 PM, Benoit Jacob wrote:

On 03/08/11 11:50 AM, Benoit Jacob wrote:

On 02/08/11 09:56 PM, Kenneth Russell wrote:
I haven't checked exactly what the site does, but could this be an
issue?

https://bugs.webkit.org/show_bug.cgi?id=64813

Basically, if the response headers contain
"Access-Control-Allow-Origin: *", then WebKit will force a reload of
the resource if it was originally fetched with a normal image request,
and subsequently fetched via CORS. (The reload is usually satisfied by
the disk cache.)

Thanks for the pointer. I know that one reason why it took us a long time to get CORS support was exactly this kind of issues with the image cache. I'll check that we pass your test.


This was a pretty recent bug fix / workaround in WebKit. Chrome 13 doesn't contain the fix, so if Chrome 13 exhibits the same behavior as Firefox, it's likely the issue.

Chrome 13.0.782.107 renders the textures normally, like Chrome 14. So this seems to be a different issue.

I've now checked that when run in Firefox, this demo does NOT set the crossOrigin attribute.

So most probably this demo is just doing different things in different
browsers.

Correction: this demo sets crossOrigin="" everywhere. The bug is in Firefox: it interprets the empty string as 'No CORS' but the spec says it should be interpreted as 'anonymous'. Fixing.


Benoit

-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------