Confirmed users
376
edits
Engagement/Developer Engagement/Grab bag/Web Components: Difference between revisions
Engagement/Developer Engagement/Grab bag/Web Components (view source)
Revision as of 09:01, 14 July 2014
, 14 July 2014no edit summary
(Created page with "Web Components are a massive change in the way we create applications and other products for the web. In essence, what Web Components allow you to do is to create your own HTM...") |
No edit summary |
||
| Line 8: | Line 8: | ||
With Web Components you can create your own HTML elements and hide complex structures and functionality in a simple element for people to use. Widgets like these are better than for example jQuery driven DOM widgets as they are part of the browser flow. The browser is busy painting a picture all the time. With DOM widgets you work against this and have to ensure that the browser gets notified of changes in your widget and paints them. With Web Components your widget already becomes part of the browser doing its job. | With Web Components you can create your own HTML elements and hide complex structures and functionality in a simple element for people to use. Widgets like these are better than for example jQuery driven DOM widgets as they are part of the browser flow. The browser is busy painting a picture all the time. With DOM widgets you work against this and have to ensure that the browser gets notified of changes in your widget and paints them. With Web Components your widget already becomes part of the browser doing its job. | ||
== Web Components in the wild == | |||
Currently Web Components are supported by Chrome and Firefox. Google are very much drivers of Web Components and created the Polymer framework to allow people to create Components that work across all modern browsers. At this year's Google IO they also announced example widgets for Polymer that match the look and feel of Android L. | Currently Web Components are supported by Chrome and Firefox. Google are very much drivers of Web Components and created the Polymer framework to allow people to create Components that work across all modern browsers. At this year's Google IO they also announced example widgets for Polymer that match the look and feel of Android L. | ||
| Line 14: | Line 14: | ||
In Mozilla, we are also 100% behind the idea of Web Components and we add more and more features to the platform. We built our own library called Brick that works out the kinks between browsers and is used to power the user interface of Firefox OS. | In Mozilla, we are also 100% behind the idea of Web Components and we add more and more features to the platform. We built our own library called Brick that works out the kinks between browsers and is used to power the user interface of Firefox OS. | ||
== Web Component resources == | |||
* [ Mozilla Brick] | * [ Mozilla Brick] | ||