Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(457)

Side by Side Diff: pkg/custom_element/lib/polyfill.dart

Issue 158083002: introduce web_components pkg for consolidated polyfills (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart
Patch Set: Created 6 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « pkg/custom_element/lib/custom-elements.min.js ('k') | pkg/custom_element/pubspec.yaml » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 // Copyright (c) 2013, the Dart project authors. Please see the AUTHORS file
2 // for details. All rights reserved. Use of this source code is governed by a
3 // BSD-style license that can be found in the LICENSE file.
4
5 /** Dart APIs for interacting with the JavaScript Custom Elements polyfill. */
6 library custom_element.polyfill;
7
8 import 'dart:async';
9 import 'dart:html';
10 import 'dart:js' as js;
11
12 /**
13 * A future that completes once all custom elements in the initial HTML page
14 * have been upgraded.
15 *
16 * This is needed because the native implementation can update the elements
17 * while parsing the HTML document, but the custom element polyfill cannot,
18 * so it completes this future once all elements are upgraded.
19 */
20 Future customElementsReady = () {
21 if (_isReady) return new Future.value();
22
23 // Not upgraded. Wait for the polyfill to fire the WebComponentsReady event.
24 // Note: we listen on document (not on document.body) to allow this polyfill
25 // to be loaded in the HEAD element.
26 return document.on['WebComponentsReady'].first;
27 }();
28
29 // Return true if we are using the polyfill and upgrade is complete, or if we
30 // have native document.register and therefore the browser took care of it.
31 // Otherwise return false, including the case where we can't find the polyfill.
32 bool get _isReady {
33 // If we don't have dart:js, assume things are ready
34 if (js.context == null) return true;
35
36 var customElements = js.context['CustomElements'];
37 if (customElements == null) {
38 // Return true if native document.register, otherwise false.
39 // (Maybe the polyfill isn't loaded yet. Wait for it.)
40 return document.supportsRegister;
41 }
42
43 return customElements['ready'] == true;
44 }
45
46 /**
47 * Loads `custom-elements.debug.js` or `custom-elements.min.js` by adding the
48 * script tag to the page. Returns a future that completes when custom elements
49 * are ready (equivalent to [customElementsReady]).
50 *
51 * Normally you should add this to your HTML file
52 * (the Polymer package will do this automatically), but loading dynamically
53 * can be useful for scenarios such as tests.
54 */
55 Future loadCustomElementPolyfill() {
56 if (!document.supportsRegister && !js.context.hasProperty('CustomElements')) {
57 var script = new ScriptElement()
58 ..src = '/packages/custom_element/custom-elements.debug.js';
59 document.head.append(script);
60 return document.on['WebComponentsReady'].first;
61 }
62 return new Future.value();
63 }
OLDNEW
« no previous file with comments | « pkg/custom_element/lib/custom-elements.min.js ('k') | pkg/custom_element/pubspec.yaml » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698