Closed joramkwak closed 11 years ago
Hey @icyxp,
We've tested IE10 and don't know of any conflicts except one: IE10 doesn't fire the error callback when it can't find a css file. If you've pulled down the entire repo, you can try the following functional test:
test/many-css-resources.html
You should see all SUCCESS except for one FAILED. That's what I see when I run IE10.
What do you see?
-- John
Hi @unscriptable, When i run the many-css-resources.html all I see is test element. From the file I can see that on success and fail, appropriate messages should be written to the document, but in my case, it fails silently. Again testing in IE9 mode, the test correctly outputs success and failed messages.
I'm running IE version 10.0.9200.16521 on windows 7 Also, it probably shouldn't matter, but the test is running via localhost
I hope this isn't the case, but it might be that IE10 behaves differently on win7 than win8. I'm going to have to find a copy of win7 somewhere, I guess. :(
@icyxp When you say localhost, are you running it via http://localhost or file:// ? Localhost doesn't generally matter, but opening the file directly very much matters as it uses different security settings.
Im using localhost not file.
On Apr 3, 2013, at 1:17 PM, Aaron notifications@github.com wrote:
@icyxp When you say localhost, are you running it via http://localhost or file:// ? Localhost doesn't generally matter, but opening the file directly very much matters as it uses different security settings.
— Reply to this email directly or view it on GitHub.
I seriously hope that isn't the issue. Ill continue testing as well and report what i find out.
On Apr 3, 2013, at 10:10 AM, John Hann notifications@github.com wrote:
I hope this isn't the case, but it might be that IE10 behaves differently on win7 than win8. I'm going to have to find a copy of win7 somewhere, I guess. :(
— Reply to this email directly or view it on GitHub.
Hey @asilvas, you haven't seen any issues in IE10, have you? -- J
I have not. With the exception of the bug fixes that went out a couple months ago. Though we're still on a pretty old version, 0.6.2a.
Hey @icyxp! Any more info about IE10 and the css! plugin?
Unfortunately no. I havent found anything new about the issue. Im trying to find a windows8 ie to try and test on. I should a able to in a week or so.
Joram
On Apr 10, 2013, at 12:09 AM, John Hann notifications@github.com wrote:
Hey @icyxp! Any more info about IE10 and the css! plugin?
— Reply to this email directly or view it on GitHub.
@unscriptable, you can close this issue. Its my fault and nothings wrong with curl.js. Apparently when I was renaming some css files, my ide automatically refactored the text 'css' wherever it saw it in my project, including the css plugin. The more ridiculous part is I redownloaded and overwrote the curl files several times but some odd type of caching on IE kept running the old js even after clearing all cache... several times over. I actually had to use a different computer to find out that it was working fine, just not on the original computer I was developing on. I'm sorry for your troubles and thank you for your help.
ROFL. Happens to the best of us, man. :) Very glad it's working! -- John
curl.js's css plugin doesn't seem to work with IE10. When css is loaded as a dependency using 'css!path/to/cssfile.css', IE10 failes to load the not only the resource but the entire module that depends on the css file, failing silently. Using developer tools, the same setup was tested as working fine in IE7 to IE9. Is this a know issue?