April 6, 2016 11:00 am

Introducing the Microsoft Edge Platform Issue Tracker

The biggest input into our roadmap for the EdgeHTML web platform is developer feedback. Your ideas and votes on User Voice, questions on Stack Overflow, tweets on Twitter, and other comments and suggestions are constantly monitored by our team to drive ongoing adjustment to our plans.

On Monday at the Edge Web Summit, we were pleased to announce our latest way for developers to provide crucial feedback and communicate openly with our team – the Microsoft Edge Platform Issue Tracker at issues.microsoftedge.com.

Screen capture showing Platform Issues on Microsoft Edge Dev with search box to find bugs or open a new bug, and a list of bugs.

Platform Issues on Microsoft Edge Dev

We receive tens of thousands of pieces of feedback daily through the Feedback Hub in Windows 10. You can reach the Feedback Hub through the “…” (‘More’) menu in Edge, under “Send Feedback. This feedback helps us identify broken sites and shapes our browser user experience through changes like the recent addition of history context menus for the back and forward buttons, pinned tabs, extensions, and more.  But web developers, browser engineers, and standards contributors also need a way to collaborate on technical platform issues, such as interoperability differences or standards incompliance.

The EdgeHTML issue tracker is designed for the web platform, with tracking for interoperability, standards impact, site outreach, and support for code snippets and markdown in repro steps. Over time, we’ll be adding more features to the tracker to make it even better for openly communicating and addressing your feedback.

This tool will replace connect.microsoft.com/ie going forward, and we have migrated open bugs from Connect to the new system. Bugs against the Chakra JavaScript engine are best directed to the ChakraCore repository on GitHub.

We built Platform Issues to address feedback that it was difficult to report issues to our team. We’re also taking steps to increase the level of communication you receive from our engineering team when reporting issues and we’ll be watching for your feedback on the new site itself. We look forward to hearing your feedback and, most of all, fixing bugs to make the web work great for you and your customers!

If you have any feedback on Platform Issues, we’d love to hear it – we’re always listening @MSEdgeDev on Twitter.

Anton Molleda and Jacob Rossi, Microsoft Edge

Updated April 6, 2016 4:03 pm

Join the conversation

  1. The markdown support is nice and the “Assigned To:” label does give some initial confidence that issues are being followed up.

    I know it’s early days but there are many small but significant problems with the site:

    – The “Participating” tab in the “Browse issues” section of the issue tracker entry page says that I’m not participating in any issues.

    – Some issues are marked as duplicates but provide no link to the other issue report(s).

    – Some issues have been *immediately* marked as “Not reproducible” without even asking for more details. This will deter other people from validating those issues, and it will deter Edge devs from following-up, even if the reporter realized a mistake in his repro steps and provided details.

    – No user-name associated with the initial issue report.

    – No date associated with the initial issue report

    – When entering a report there is no “Description” field or option for explicitly suggesting work-arounds. The old-site had these.

    – A lot of issues are copied from the old-site but without descriptions / validations / comments / work-arounds and without links to the original report. Important information is being lost. Also, there are some invalid links from issues on the old-site to the re-entered issue on the new-site.

    – If I search for an issue the results are limited to 50 entries and there is no way to see more, either by paging or dynamically loading

    – The old site had an advanced search where you could search by status, date, etc.

    • There is an advanced search method, it just lacks a graphical user interface. Search for –
      [status:inprogress]
      For example.

      I agree with all of the other points.

  2. Favourites import from Firefox is a great step forward. Synch with Mozilla account would be better. Also:
    1. Very clumsy process adding them into a “Imported from Firefox\Bookmarks” folder rather than straight into the Favourites Bar. Would be nice to map them straight onto the Favourites Bar, or at least provide a target folder option. De-duplication check would be handy as well.
    2. Drag and drop from “Imported from Firefox” bookmarks onto Favourites Bar is dodgy. Works for about 3 or 4, then graphics freeze, program hangs => exit and re-start browser. No permanent damage apparent to bookmark items.

  3. Anything to improve/do away with connect.* is a welcomed change and improvement. MSFT really needs to improve developer relations/engagement all around, starting with its blogging system (please join the rest of the internet and use Disqus!), and even UserVoice leaves much to be desired. There needs to be a group dedicated to doing exactly this.

    With all of this said, I feel MSFT has done a fantastic job in the past year especially with improving developer engagement and reaching out to developers using the tooling and technology available to them. There is a lot to improve upon, and hopefully tools/ideas/products like the new issue tracker here evolve accordingly and meet the required demand in this most important/valuable of spaces.