What happens to Web Components (Custom Elements and Shadow DOM) in unsupported browsers?
In this screencast I'm creating a Custom Element with Shadow DOM
from scratch and run the sample in Firefox, Safari and Chrome. Patching (aka polyfill) included:
After covering the "basics" in WebStandards igniter, now 50+ episodes of continuous Web Components (Custom Elements, Shadow DOM, CSS 3 styling, Templates, ES 6 imports) coding workshop is available: webcomponents.training.
No installation, no dependencies, no builds: only vanilla web (browser) standards, without any external frameworks or dependencies, were used.
Are you already building, or still migrating? Learn once, apply anywhere :-):
In this screencast I created a Java EE 8 application with JAX-RS endpoint and JSON-B serialization from scratch, then developed
a Custom Element (part of the Web Components specification) which talks to
the Java EE 8 backend in 6 mins. No external dependencies were used in frontend and backend.
4th episode "Micro Java EE" of airhacks.fm podcast with special guest, Payara CEO, Steve Millidge is available.
We discussed Microservices, Cloud Native Java EE, Microprofile, EE4J, Thin WARs, Ueber JARS and Fat JARs.