Method for registering (creating) custom elements in script.
See http://blogs.windows.com/msedgedev/2015/07/14/bringing-componentization-to-the-web-an-overview-of-web-components/ (part 1) and https://blogs.windows.com/msedgedev/2015/07/15/microsoft-edge-and-web-components/ (part 2) for more information on our Web Components thoughts, plans, and roadmap.
Saleh Abdel Motaal commented
Microsoft, stop throwing tantrums, honestly, you will break the web, and now with GitHub, open source all together.
Tufik Chediak commented
Mm, Microsoft always giving problems to developers and the future of the web. Come on guys, now all browsers support this features, but you always keep resistance.
Judd Younce commented
I'm not here to bash Microsoft Edge. However I am here to QUESTION YOUR INTEGRITY. According to your about page (at this time) your mission statement is:
Microsoft’s Mission Statement:
"Our mission is to empower every person and every organization on the planet to achieve more."
Your mission statement is exactly what Custom Elements and Shadow Dom do. So why are they not available in Microsoft Edge?? They are the top 2 most requested features. Thousands of votes ahead of the rest!
Since there are tens of thousands of people who have upvoted for them, that means that there are hundreds of thousands of people who want them.
Come on guys!
Tyler Graf commented
Please please add support for custom elements and shadow dom.
Caleb Williams commented
This is the future of the web platform. Once these are properly implemented (along with shadow DOM) the need for expensive frameworks decreases dramatically. This needs to be implemented as soon as possible.
Aki Rodic commented
I am a few weeks away from shipping a product that does not work on Edge because of this. Come on Microsoft, you can do this!!!
Mike Bechtel commented
In order for Edge to survive, start implementing what other browsers have and not be the only one still hanging onto old ideals of web browsing. Web dev is much as important if not more than casual user experience. Web Components should have been a long time ago as this is not a new thing, just becoming more necessary.
Jan-Erik Vinje commented
The medium post of Andreas Galster: (first time I gave 50 claps to anyone ) https://medium.com/@andreas_66372/dear-satya-nadella-im-a-web-developer-and-deeply-disappointed-with-the-edge-team-beffd5308768
Andreas Galster commented
Hi everyone, FYI I got in touch with the team via an open letter, they said they will be writing a blog post in the next weeks with an update on the roadmap.
Stay tuned, we should see some news what the plans are in the next weeks :).
...Even Safari has this now, this is embarrassing.
No Polyfill please
There has to be a reason why this (and shadow dom) is on the backlog still. Is there a technical reason in Edge that makes this not feasible to adapt at this time.
Me and a few other devs expected they were going to announce support at MS Build, but nothing. It's definitely cool to see all the fancy VR/MR stuff presented, but to devs this should be ranked much higher and it seems to be ignored.
Eric Pias commented
+1. We see the value of web components and are including them in our development strategy going forward. Edge performance using polyfills is a major concern. Please prioritize this.
JP Lew commented
pewdiepie brought me here
Monitor it's current status directly on the Edge Platform here:
today CustomElements are 'under consideration'
No more polyfill please
This is definitely a crucial feature that's needed in the modern web. Let's make it happen :)
'ON THE BOARD' please
Saravana Kumar Narayanan commented
We need it ASAP !!!!
Luciano Pérez Cerra commented
implement ASAP : => Custom Elements && Shadow Dom