Manuel Razzari wrote: > It turns out that some of the imports actually produce HTTP requests > from IE7, like this: GET > /contents/styles/_url(%22chaos-060801-test2.css%22) > > The resulting 404 page is actually parsed by IE7 as CSS... so if you > have some custom 404 page with embedded CSS, it will be applied by > IE7, with obviously unpredictable results...
Interesting. Thanks for the information. Looks like the oversimplified blocking of the 'leading underscore' hack implemented in IE7, has unintentionally provided us with another way to serve version-specific stylesheets to IE7. Lack of testing of "what will actual happen when..." on the IE7 team's part, is to blame, I guess. The obvious chaos the lack of an actual stylesheet with the right, garbled, name may lead to, shows that "the cure" can be worse than "the disease" - as is often the case. Hacking browsers that their creators have already hacked to pieces, tends to lead to unpredictable results. I don't use the 'leading underscore' hack for @imports in the real world myself, but it looks like name-garbling similar to what IE/win does for the valid @import hack (which I use quite regularly)... <http://www.gunlaug.no/contents/wd_additions_12.html> ...which means a real or dummy CSS file with the garbled name will also "solve" it. regards Georg -- http://www.gunlaug.no ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
