New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 595148 link

Starred by 1 user
Status: WontFix
Owner:
█ y...@yoav.ws
Last visit > 30 days ago
Closed: May 2016
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Preloaded fonts from same-origin should not need a 'crossorigin' attribute in order to match

Project Member Reported by y...@yoav.ws, Mar 15 2016 
Version: 51
OS: All

test case - http://test.weissyoav.com/tests/preload/same-origin-font.html

Same origin font preload shouldn't need to add a 'crossorigin' attribute in order to match the following request, and avoid double downloads. Currently that is not the case, which is confusing and wrong.

Comment 1 by y...@yoav.ws, May 30 2016

Status: WontFix (was: Assigned)
It seems like there are fundamental issues here that do require this crossorigin attribute: https://codereview.chromium.org/1801513003/#msg8

Since corsEnabled requests to the same origin can be redirected to a cross-origin host we cannot blindly match corsEnabled and non-cors requests to the same origin at request time. That means that if we wanted to support removing the attribute, we have to come up with new and fairly complex response time matching mechanisms that do not exist today. Therefore (sadly) WONTFIXing this.
►

Sign in to add a comment