This is, in short, the justification for just about every other nonstandard IE behavior. It made somebody’s life easier assuming you were willing to cater to IE. Since prefetching won’t work for a large share of today’s browsers (as I understand it), the way forward is to build a new solution, not rely on an old IE feature.
I think you could portably accomplish this by creating invisible iframes with “src=script.js” and then load a script tag later, but my first effort would be to reduce the number of scripts I’m loading to dodge the problem entirely.
This is, in short, the justification for just about every other nonstandard IE behavior. It made somebody’s life easier assuming you were willing to cater to IE. Since prefetching won’t work for a large share of today’s browsers (as I understand it), the way forward is to build a new solution, not rely on an old IE feature.
I think you could portably accomplish this by creating invisible iframes with “src=script.js” and then load a script tag later, but my first effort would be to reduce the number of scripts I’m loading to dodge the problem entirely.
It’s worth pointing out that the author has proposed standardizing an equally performant alternative.