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,489 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]Jonathan Sampson [MSFT] shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    98 comments

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

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

      • Andreas GalsterAndreas 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?

      • camlokencamloken 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.

      • Dan HolmesDan Holmes commented  ·   ·  Flag as inappropriate

        To those who think that Microsoft doing its own browser is a waste... keep in mind that browser competition (which Microsoft originally started) was the basis for the modern web today. Keeping competition in the web browser space is a good thing for the modern web as it promotes industriousness and competition, keeping the platform very much alive!

      • govisgovis commented  ·   ·  Flag as inappropriate

        It seems ironic how Microsoft said they were ready to get behind the advanced Web platform when it's abandoned its own proprietary platform for building Web apps, Silverligt, that used to offer custom elements, declarative composition, data binding, visual and shadow element trees - much like modern Web technologies such as Web Components do today. And now it's the only major Web Browser vendor pulling back on some these very advanced features in the Web platform.

        I strongly think that somebody at Microsoft ought to put its money where its mouth is or seriously consider quitting the Web Browser game.

      ← Previous 1 3 4 5

      Feedback and Knowledge Base