How can we improve the Microsoft Edge developer experience?

Custom Elements

Method for registering (creating) custom elements in script.

Spec: http://www.w3.org/TR/custom-elements/

13,690 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 →

    128 comments

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

        Microsoft, stop throwing tantrums, honestly, you will break the web, and now with GitHub, open source all together.

      • Tufik Chediak commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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!

        https://www.microsoft.com/en-us/about

      • Caleb Williams commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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.

      • Andreas Galster commented  ·   ·  Flag as inappropriate

        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 :).

      • Templarian commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        +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.

      • Mark commented  ·   ·  Flag as inappropriate

        This is definitely a crucial feature that's needed in the modern web. Let's make it happen :)

      ← Previous 1 3 4 5 6 7

      Feedback and Knowledge Base