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

Side by Side Diff: polymer_1.2.3/bower_components/webcomponentsjs/README.md

Issue 1581713003: [third_party] add polymer 1.2.3 (Closed) Base URL: https://chromium.googlesource.com/infra/third_party/npm_modules.git@master
Patch Set: 1.2.3 Created 4 years, 11 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
OLDNEW
1 webcomponents.js 1 webcomponents.js
2 ================ 2 ================
3 3
4 [![Join the chat at https://gitter.im/webcomponents/webcomponentsjs](https://bad ges.gitter.im/Join%20Chat.svg)](https://gitter.im/webcomponents/webcomponentsjs? utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) 4 [![Join the chat at https://gitter.im/webcomponents/webcomponentsjs](https://bad ges.gitter.im/Join%20Chat.svg)](https://gitter.im/webcomponents/webcomponentsjs? utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
5 5
6 A suite of polyfills supporting the [Web Components](http://webcomponents.org) s pecs: 6 A suite of polyfills supporting the [Web Components](http://webcomponents.org) s pecs:
7 7
8 **Custom Elements**: allows authors to define their own custom tags ([spec](http s://w3c.github.io/webcomponents/spec/custom/)). 8 **Custom Elements**: allows authors to define their own custom tags ([spec](http s://w3c.github.io/webcomponents/spec/custom/)).
9 9
10 **HTML Imports**: a way to include and reuse HTML documents via other HTML docum ents ([spec](https://w3c.github.io/webcomponents/spec/imports/)). 10 **HTML Imports**: a way to include and reuse HTML documents via other HTML docum ents ([spec](https://w3c.github.io/webcomponents/spec/imports/)).
(...skipping 105 matching lines...) Expand 10 before | Expand all | Expand 10 after
116 don't work, despite working under native Shadow DOM. The solution is to use `pol yfill-next-selector` like: 116 don't work, despite working under native Shadow DOM. The solution is to use `pol yfill-next-selector` like:
117 117
118 ``` 118 ```
119 polyfill-next-selector { content: '.foo :host.bar, :host.foo.bar'; } 119 polyfill-next-selector { content: '.foo :host.bar, :host.foo.bar'; }
120 ``` 120 ```
121 121
122 ### execCommand and contenteditable isn't supported under Shadow DOM <a id="exec command"></a> 122 ### execCommand and contenteditable isn't supported under Shadow DOM <a id="exec command"></a>
123 See [#212](https://github.com/webcomponents/webcomponentsjs/issues/212) 123 See [#212](https://github.com/webcomponents/webcomponentsjs/issues/212)
124 124
125 `execCommand`, and `contenteditable` aren't supported under the ShadowDOM polyfi ll, with commands that insert or remove nodes being especially prone to failure. 125 `execCommand`, and `contenteditable` aren't supported under the ShadowDOM polyfi ll, with commands that insert or remove nodes being especially prone to failure.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698