Shadow DOM (unprefixed)
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.
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!
Michael Klein commented
What is going on here? The last blog article is from 2015? Are you kidding me??
Jan-Erik Vinje commented
So its been a few weeks since Microsoft were supposed to have blogged about what they are doing.... Andreas Galster indicated in early June that he heard from someone in Microsoft that they were planning to post something...
Caleb Williams commented
Super disappointed this hasn't been at least committed to yet. This is the future of the web platform. Would love to see Edge implement as soon as possible.
Yevgeniy Okun commented
Here is why this needs to be implemented.
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 :).
Michael DePouw commented
@Admin - I appreciate those blog posts and they are very informative but they are now 3 years old. Any updates? Any new blog posts to share?
"Not only will the DOM upgrade enable better internal extensibility for future web components technologies, but it will provide a baseline for next generation performance in the DOM of Microsoft Edge."
Has the new DOM been implemented?
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.
Joseph Chappell commented
Please folks slate this for a release, or at a minimum make an issue that shows it is in a back log somewhere..where the 12,000 + developers that are the leadership of how the web is presented around the world, can have some information to plans their lives and businesses.
O.J. Sousa Rodrigues commented
Chukkrit Visitsaktavorn commented
How is it going now, any progress?
James Walker commented
Still "under consideration" on platform status!?
Apparently to hard to implement for Microsoft?! Any news?
Pert Simmens commented
edge will meet the same fate as the ie as long ms does not support such quality features for years...
Nick Dugger commented
Native web components with Shadow DOM are the next step in the natural evolution of web applications. Does MS really want Edge to just become the next version of IE, where it constantly lags behind the progressive web? Get your act together, or just give up so we can support only browsers that actually matter.
Nearly 12,000 votes and its still "Under Consideration". What a joke of a website.
More than 2 years later, no communication at all, this unbelievable ... could you ******** please say a word?
Edge market share is at under 4% and approach the team has chosen is not helping. We may have to hang on a bit longer until legacy browsers are phased out
I never use "Set these tabs aside" or "Show tab previews". I need Shadow DOM and Custom Elements.