Web Components: a German conference.
Ever get into a conference room, only to realize that you are not the target audience?
I made the best of it. Here is my attempt at understanding a German talk on web components.
LEGOS! ON THE SCREEN.
“standards” *air quotes” hehehehe…standards.
“the web platform is gone”
implementation, abstract, dom. dom is relatively stable.
clone, done, dom.
it’s good in everything except Internet Explorer…hehehe…Internet Explorer.
There are no exploits!
nein. why? nein? why? no, because. but I have a question…here’s a coffee. Please have respect for the browser.
github, time element in browser, three hours ago, five hours ago. the newspaper. the custom elements, time is time ago. twenty two? API changes. may change soon. API changes, all is on board. Polyfill…small. when the web components, completed, villain, polyfill, performance, functions with API and then the API is relatively stable and then Polyfill…
Welcome to the Shadow Dom
this is a…feature. encapsulates, no. document query selector, it can ID what you have in the shadow dom. but it clashes. color red, document blind. all.
child, shadow roots, and the H1 is nested in the. then we have a newsbox component. the template is the component. breaking news. newsbox and then we have div, yes, here, something causes, news. enterJS. started.
and then it’s like what? content element. query selector, two, two elements in my document. in the shadowroot.
omfg, BBQ, Big news! Boring things happened.
We have components, good. practice, practice. the problem is that the shadow dom is filled with problems, document, doc, parent, it has children and siblings. Shadown dom has, when my browser has, regular, inspectors, no. shadow roots happen in the performance, it’s…is it polyfillable? not sure it’s a good value. implement, extreme.
we have a war, and then JS.
this is so elegant, porcelain.
apple and microsoft strongly disagree and then Google said ship it. so mailing list bomb. we ship! experiment. polyfill is good for polymer.
together, we look at the status quo. we have polyfill, mega optimistic, all is good obviously. we have polyfill-ish, Chrome, come at me bro, we’re live, yes, can’t hear you.
not without under consideration.
Chrome releases. my two cents is that, web components, barcelona, single track conference. noooo, slides, web components, was it small? Chrome went yes! one minute, all is good.
15, the inspiration, twitter, negative blog posts. but web components, element, frameworks, angular has component, compatible, weird, dazzled.
the problem here is that from web3C. this Finnish is good for all of us. no! But then Facebook post and Github post. because. this discussion please, you are welcome, this is good, Github. no. no. no. this is not. that’s my side of things.
mobile that UI
Google has 4, mozilla has, VR content in, scene, camera, box, this is relatively cool.
Here comes the hot shit. california software, his name is. new IE 6. what, this is…sucks. FYI, for you the shadow dom specs are presented. specs by custom elements.
but all the elements end up in the buggy. What? Thanks. Fine. Thanks. But there’s an alternative. the open and close mode.