This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From: http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0664.html, http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0689.html, http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0703.html In today's world, using <link> bears assumptions, such as that it won't run script. We're changing these, and we need to be careful.
<link> doesn't do anything on its own. It only does something when combined with specific values, some of which (e.g. rel=stylesheet) have run script in the past.
(In reply to comment #1) > <link> doesn't do anything on its own. It only does something when combined > with specific values, some of which (e.g. rel=stylesheet) have run script in > the past. Re: In the past -- this is with IE behaviors and expressions, right?
(In reply to comment #2) > (In reply to comment #1) > > <link> doesn't do anything on its own. It only does something when combined > > with specific values, some of which (e.g. rel=stylesheet) have run script in > > the past. > > Re: In the past -- this is with IE behaviors and expressions, right? Or this one? http://en.wikipedia.org/wiki/JavaScript_Style_Sheets
Given that this existed in the web for a while, I think we should keep moving forward with <link rel=import>