3 ms·

Hopefully they've also gotten better people triaging the bugs than in the past. Too many times I've opened one-liner JS bugs with references to the specificati

Hopefully they've also gotten better people triaging the bugs than in the past. Too many times I've opened one-liner JS bugs with references to the specification that get closed because they need a public website to repro. I've even had bugs which link to the failing W3C spec test get closed as 'not repro'. I used to work at MS and was often thanked for the quality of the bugs I opened (frequently IE bugs!). They must have different people triaging the publicly submitted bugs because I'm pretty sure they don't know how to even open the dev tools.

NegativeLatency 10y ago
Sounds like Microsoft.
- gregwhitworth 10y ago
  The Edge platform team will be triaging them, I am one of them that has been triaging them. One suggestion is to ensure that it is truly a reduction, we built this for webdevs that have reductions and just don't want to file them and we don't want to miss out on those. On your statement though regarding them being closed out. How long ago was that?
- j4_james 10y ago
  Is it really any better for other browsers though? I know I've encountered a fair share of webkit bugs that have been confirmed yet still left unresolved for years on end. And they also aren't above closing bugs as wontfix that clearly are genuine problems. Obviously that's anecdotal, but I'd be curious to see someone do an analysis of turnaround times on the public bug trackers. It may not be feasible to detect incorrectly closed bugs, but a measure of the time taken to resolve confirmed bugs could be an interesting statistic.
bentlegen 10y ago
I opened up an issue re: window.onerror on their previous bug tracker at the end of last year: https://connect.microsoft.com/IE/feedbackdetail/view/2051728/window-onerror-missing-error-object-5th-argument https://connect.microsoft.com/IE/feedbackdetail/view/2051728... That issue has since been closed and "moved" to another URL. But the new URL is a broken link, and I cannot find the new issue via search (if it was created at all). I've since spoken to Edge program managers about the issue, who've assured me it will be taken care of, but so far no progress has been made (possibly because it is no longer tracked). (Raising this again here in hopes it will be noticed.)
- jongalloway2 10y ago
  Is it a dupe of this one? https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/817828/ https://developer.microsoft.com/en-us/microsoft-edge/platfor...
  - bentlegen 10y ago
    Yes, thank you! > Reported by 0 people :(

NegativeLatency 10y ago

Sounds like Microsoft.

gregwhitworth 10y ago
The Edge platform team will be triaging them, I am one of them that has been triaging them. One suggestion is to ensure that it is truly a reduction, we built this for webdevs that have reductions and just don't want to file them and we don't want to miss out on those. On your statement though regarding them being closed out. How long ago was that?
j4_james 10y ago
Is it really any better for other browsers though? I know I've encountered a fair share of webkit bugs that have been confirmed yet still left unresolved for years on end. And they also aren't above closing bugs as wontfix that clearly are genuine problems. Obviously that's anecdotal, but I'd be curious to see someone do an analysis of turnaround times on the public bug trackers. It may not be feasible to detect incorrectly closed bugs, but a measure of the time taken to resolve confirmed bugs could be an interesting statistic.

bentlegen 10y ago

I opened up an issue re: window.onerror on their previous bug tracker at the end of last year: https://connect.microsoft.com/IE/feedbackdetail/view/2051728/window-onerror-missing-error-object-5th-argument https://connect.microsoft.com/IE/feedbackdetail/view/2051728... That issue has since been closed and "moved" to another URL. But the new URL is a broken link, and I cannot find the new issue via search (if it was created at all). I've since spoken to Edge program managers about the issue, who've assured me it will be taken care of, but so far no progress has been made (possibly because it is no longer tracked). (Raising this again here in hopes it will be noticed.)

jongalloway2 10y ago
Is it a dupe of this one? https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/817828/ https://developer.microsoft.com/en-us/microsoft-edge/platfor...
- bentlegen 10y ago
  Yes, thank you! > Reported by 0 people :(