How can we improve the Microsoft Edge developer experience?

Shadow DOM (unprefixed)

Enables DOM tree encapsulation. Without it, widgets may inadvertently break pages by using conflicting CSS selectors, class or id names, or JavaScript variables.

http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html

11,888 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jonathan Sampson [MSFT] shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    104 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Rob commented  ·   ·  Flag as inappropriate

        Apparently to hard to implement for Microsoft?! Any news?

      • Pert Simmens commented  ·   ·  Flag as inappropriate

        edge will meet the same fate as the ie as long ms does not support such quality features for years...

      • Nick Dugger commented  ·   ·  Flag as inappropriate

        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.

      • oliver commented  ·   ·  Flag as inappropriate

        Nearly 12,000 votes and its still "Under Consideration". What a joke of a website.

      • toplam commented  ·   ·  Flag as inappropriate

        More than 2 years later, no communication at all, this unbelievable ... could you ******** please say a word?

      • Anonymous commented  ·   ·  Flag as inappropriate

        I never use "Set these tabs aside" or "Show tab previews". I need Shadow DOM and Custom Elements.

      • Oeno commented  ·   ·  Flag as inappropriate

        Can we have a new update for goodness sake? The last update was in 2015.

      • Andreas Galster commented  ·   ·  Flag as inappropriate

        Dear Edge team, we understand you are busy but not giving updates at all is very disappointing, to say the least. You said two years you're on this, your latest post on what's next doesn't even mention webcomponents at all.

        Perhaps you are too busy to still refactor some DOM architecture, but this is not helping. At least give us an update. Our site runs fine on all browsers except for yours, since the webcomponents polyfills don't work 100% correct. Can you please give an update when we can expect to see this in a windows insider build?

      • camloken commented  ·   ·  Flag as inappropriate

        I use React. I love it, but it doesn't solve the encapsulation problem (eg. encapsulating basic styles). React components can only be used in React, so the problem of reusing standard components still remains. Encapsulation is one step in the right direction.

      ← Previous 1 3 4 5 6

      Feedback and Knowledge Base