25007 2014-03-11 17:23:31 +0000 [imports]: Want New LinkImport method to return a promise. 2015-07-06 08:03:20 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED MOVED P2 normal --- 23278 1 morrita dglazkov d jaffathecake mike public-webapps public-webapps-bugzilla oldest_to_newest 102213 0 morrita 2014-03-11 17:23:31 +0000 There should be a way to wait an import being loaded using Promise. This might be better to be a part of HTML standard, but it's fine to start from here. 102362 1 jaffathecake 2014-03-14 10:17:06 +0000 Some details from the discussion at http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2014-March/042201.html * This should be .loaded(), "ready" will be used for non-load events, such as document.ready() * This should reject with InvalidStateError if href isn't set Should promise-vending functions without arguments take onFulfilled & onRejected callbacks? Eg, it's currently: var promise = link.loaded().then(onFulfilled, onRejected); Should we allow: var promise = link.loaded(onFulfilled, onRejected); 102376 2 d 2014-03-14 14:35:01 +0000 > Should promise-vending functions without arguments take onFulfilled & onRejected callbacks? I don't like this. It's a needless inconsistency in the platform that sometimes you'll be interfacing with promise objects through the normal interface and sometimes you'll be bypassing that. 104846 3 dglazkov 2014-04-30 19:16:54 +0000 Maybe replace .import with this? 104899 4 jaffathecake 2014-05-01 08:00:22 +0000 I'm hoping we can get .loaded() on other link types (CSS, rel=preload), see http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2014-March/042201.html Not against .import() vending a promise though, especially if a general .loaded() method meets resistance or apathy. 106434 5 jaffathecake 2014-05-20 10:22:19 +0000 In http://dev.w3.org/csswg/css-font-loading/#dom-fontface-loaded .loaded is a property, not a method. link.loaded should be a property for consistency. 121626 6 hayato 2015-07-06 08:03:20 +0000 Moved to https://github.com/w3c/webcomponents/issues/212