Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IE7 Access is Denied error with network-path references ("//example.com/example.css") #70

Closed
wants to merge 1 commit into from

Conversation

rudidude86
Copy link

It seems to me like the regular expression on line 48 that's checking to see whether a stylesheet's href is external or not doesn't correctly identify "protocol-less" network-path references as being external. For instance, suppose I'm including some YUI CSS file from Google's CDN (and I want to fetch it using whatever protocol the page was delivered in), in my link tag, I would set the href to this: "//ajax.googleapis.com/ajax/libs/yui/2.9.0/build/base/base-min.css"

Respond.js erroneously thinks this is a local file and adds it to the requestQueue, and in IE7, I see an "Access is denied" error on the page.

I believe my updated regular expression correctly treats network-path references as external while still treating everything else the same (though I would love to have other people take a look at it and make sure).

… to see whether a stylesheet's HREF is external or not doesn't correctly identify "protocol-less" network-path references as being external. For instance, suppose I'm including some YUI CSS file from Google's CDN (and I want to fetch it using whatever protocol the page was delivered in), in my LINK tag, I would set the HREF to this: "//ajax.googleapis.com/ajax/libs/yui/2.9.0/build/base/base-min.css"


Respond.js erroneously thinks this is a local file and adds it to the requestQueue. When I include this on a page in IE7, I see an "Access is denied" error on the page.

I believe my updated regular expression correctly treats network-path references as external while still treating everything else the same (though I would love to have other people take a look at it and make sure).
@scottjehl scottjehl closed this in c6ee894 Jan 27, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants