22407 2013-06-19 18:04:39 +0000 [imports]: Consider implications of changing the meaning of <link> with rel=import 2013-09-18 20:43:49 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED WONTFIX P2 normal --- 20683 1 dglazkov dglazkov ian morrita w3c zcorpan public-webapps-bugzilla oldest_to_newest 89594 0 dglazkov 2013-06-19 18:04:39 +0000 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. 90636 1 ian 2013-07-11 16:28:05 +0000 <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. 90944 2 dglazkov 2013-07-18 20:14:57 +0000 (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? 91111 3 morrita 2013-07-23 02:11:03 +0000 (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 93537 4 dglazkov 2013-09-18 20:43:49 +0000 Given that this existed in the web for a while, I think we should keep moving forward with <link rel=import>