11 ms·

I can echo his experience reporting browser bugs and provide my own reviews: Firefox - By far the best. Quick response, usually from engineers. If it's importa

I can echo his experience reporting browser bugs and provide my own reviews: Firefox - By far the best. Quick response, usually from engineers. If it's important the fix will be quick. Edge - No reply for months / years. When I've gotten replies back it's been to ask me to try with the current version. When I do and the bug still exists it goes back at the bottom of the queue it seems. Chrome - Somewhat of a mixed bag. Some times responses are quick, some times they are from engineers. But most often I get replies that convey the person I'm speaking too is a very green QA type. I've gotten replies that the test case I provided them doesn't reproduce the bug, because they had attempted loading it with the file:// protocol (of course hardly anything works with the file protocol). I'm not sure, do they expect me to include a web server for them? Safari - Only tried a couple of times, never gotten a whisper back. I would rate my experiences as: Firefox - A+ Chrome - C Edge - D Safari - F

jaffathecake 8y ago
Yeah that Chrome experience doesn't sound great. Fwiw I tend to put my test cases on jsbin or Glitch, but yeah, a Chrome engineer should know to put the page on a basic web server. If anyone runs into problems like this, feel free to bug one of the Chrome dev rel folks, such as me.
- MatthewPhillips 8y ago
  Like I said, my impression is that often the people replying are not engineers. Here's one with that problem: https://bugs.chromium.org/p/chromium/issues/detail?id=674096#c8 https://bugs.chromium.org/p/chromium/issues/detail?id=674096...
  - jaffathecake 8y ago
    Yeah, that's not great, but the commenter in #12 is a senior engineer on devtools, so at least the right person saw it in the end.
    - bjornstar 8y ago
      https://bugs.chromium.org/p/chromium/issues/detail?id=674096#c12 https://bugs.chromium.org/p/chromium/issues/detail?id=674096... was an assignment 6 months ago. It's still open after 2.5 years. I would not call this a good outcome.
      - jaffathecake 8y ago
        Sure, but priorities are a thing. I don't think it's fair to compare this to an origin model exploit.
        MatthewPhillips 8y ago
        Yeah, this is a UI bug in devtools for a feature not a lot of people use. Plus web worker bugs always get pushed to the bottom of the queue for every browser. So I don't have any problem with how long my weird issues take to get fixed. It's more about comparing to Firefox where you usually get a quick response which at least conveys that the person on the other end understands what is being reported. I'm fine with the eventual outcome here. A comment acknowledging that it's a real bug (or not) would have been better, but being assigned to someone sort of acknowledges that, I guess.
        oblio 8y ago
        > Plus web worker bugs always get pushed to the bottom of the queue for every browser. Why is that?
        philipwhiuk 8y ago
        It's pretty rare to use in user-code. It might be well used in libraries, but I guess the standard developer experience is using libraries not writing them.
        abritinthebay 8y ago
- paulddraper 8y ago
  I have an S3 bucket for mine. E.g. a js closure memory leak: https://bugs.chromium.org/p/chromium/issues/detail?id=315190 https://bugs.chromium.org/p/chromium/issues/detail?id=315190 https://s3.amazonaws.com/chromebugs/memory.html https://s3.amazonaws.com/chromebugs/memory.html
  - myfonj 8y ago
    Whoa, that page crashed my (long running) Nightly (presumably exhausted RAM completely) and in freshly started got 4 GB for the tab process (and survived). Nice.
- reitanqild 8y ago
  > If anyone runs into problems like this, feel free to bug one of the Chrome dev rel folks, such as me. Hi, and thanks for being part of creating Chrome && reaching out here. Now that I have a Chrome guy here maybe you can help with another annoying issues: -QC internally at Google seems to be blissfully unaware of the fact that other browsers exists. Examples: - one glaring issue I'm running into in core Angular on a daily basis. - Google Calendar performance is sometimes unreasonably slow in Firefox - For weeks or months Google search results would drive once CPU core to 100% twice a minute.
  - notatoad 8y ago
    none of those are something a chrome dev rel person can help you with. People like you are the reason we have to deal with three layers of low-level tech support before we can actually talk to somebody who knows what they're doing - please don't just spray your random complaints at anybody who happens to be related to google in any way.
    - gsnedders 8y ago
      And it's not like the Chrome dev rel team doesn't fight for these things, but ultimately the Chrome team doesn't have any control of prioritisation of bugs in other products (like Calendar). The only way we're going to see a significant change is when those high up in the Google org chart start caring about products working well in other browsers; as long as it's up to each individual product we'll continue to see products prioritising time-to-market and targeting only the browser with the majority of the market.
      - reitanqild 8y ago
        That's the second reason to post it here: because if you see one googler there are hundreds nearby, and some of them might be at the relevant team. (And if I point out often enough what happened last time a mega corp abused their position to market their browser then maybe some of them starts talking about it internally?)
    - 8y ago
robotmlg 8y ago
Did you report the Safari bug to Apple or to WebKit.org? I've had good luck getting responses and fixes from the webkit guys
- Rodd45 8y ago
  They seem to get the things done professionally and effectively.
CryoLogic 8y ago
I reported a very serious one to Edge recently and the team told me they would "backlog it and might be on a future release". Chrome had already patched it and Firefox never had it. (It was related to incorrect DOM spec implementation of document inheritance allowing cookie access from anywhere). I'll do a full write up and blog it when I'm back from vacation but to summarize I was really unimpressed by the team at Edge and Microsoft Security.
driverdan 8y ago
Did you include a 90 day public disclosure window?
deleted 8y ago
[deleted]
robocat 8y ago
Personally over many bug reports and many years: A+ experience with the Chrome team E with Edge F with Safari The Chrome devs have been astonishingly good. My experience has repeatably been that if they are given a good bug report, they get it fixed and often fix it really fast. Or they reply with excellent technical reasons why not. Also multiple times I have seen extreme corner-case regressions get magically fixed without me reporting anything! Edge - always waffle and misdirection in reply to bug reports. I only bother to give them very well documented, repeatable bugs, plus attached repro file, for things I really need fixed. However: I did have one good experience recently because I reported the bug for the Edge beta, on a feature they were actively working on catching up to the other browsers (however they still had poor interaction). Safari: hopeless. Report a critical bug with excellent repro file, and get no response, and no fix. No rating for Firefox because I haven't bothered reported any bugs to them in the last few years. Edit: this is for non-security related bugs.
- odbol 8y ago
  Apple hears ya, Apple don't care.
  - masklinn 8y ago
    Yeah apparently from people familiar with the deep black hole that is Radar you're supposed to keep submitting bugs, dupes count as a vote or something. It sounds absolutely horrendous.
- ikeboy 8y ago
  I once reported a chrome issue. Got no attention until I found a different issue I thought was related and commented there, which got the attention of someone competent who realized it was a hardware bug they'd fixed before but had a regression. Not a security bug, just that a very large number of websites didn't load.
userbinator 8y ago
In other words, the experience gets progressively worse the bigger the company. I'm not surprised, having worked in companies of that scale the amount of bureaucracy and general red-tape to do the smallest of things is absolutely irritating.
mito88 8y ago
and Samsung's browser?

jaffathecake 8y ago

Yeah that Chrome experience doesn't sound great. Fwiw I tend to put my test cases on jsbin or Glitch, but yeah, a Chrome engineer should know to put the page on a basic web server. If anyone runs into problems like this, feel free to bug one of the Chrome dev rel folks, such as me.

MatthewPhillips 8y ago
Like I said, my impression is that often the people replying are not engineers. Here's one with that problem: https://bugs.chromium.org/p/chromium/issues/detail?id=674096#c8 https://bugs.chromium.org/p/chromium/issues/detail?id=674096...
- jaffathecake 8y ago
  Yeah, that's not great, but the commenter in #12 is a senior engineer on devtools, so at least the right person saw it in the end.
  - bjornstar 8y ago
    https://bugs.chromium.org/p/chromium/issues/detail?id=674096#c12 https://bugs.chromium.org/p/chromium/issues/detail?id=674096... was an assignment 6 months ago. It's still open after 2.5 years. I would not call this a good outcome.
    - jaffathecake 8y ago
      Sure, but priorities are a thing. I don't think it's fair to compare this to an origin model exploit.
      - MatthewPhillips 8y ago
        Yeah, this is a UI bug in devtools for a feature not a lot of people use. Plus web worker bugs always get pushed to the bottom of the queue for every browser. So I don't have any problem with how long my weird issues take to get fixed. It's more about comparing to Firefox where you usually get a quick response which at least conveys that the person on the other end understands what is being reported. I'm fine with the eventual outcome here. A comment acknowledging that it's a real bug (or not) would have been better, but being assigned to someone sort of acknowledges that, I guess.
        oblio 8y ago
        > Plus web worker bugs always get pushed to the bottom of the queue for every browser. Why is that?
        philipwhiuk 8y ago
        It's pretty rare to use in user-code. It might be well used in libraries, but I guess the standard developer experience is using libraries not writing them.
        abritinthebay 8y ago
paulddraper 8y ago
I have an S3 bucket for mine. E.g. a js closure memory leak: https://bugs.chromium.org/p/chromium/issues/detail?id=315190 https://bugs.chromium.org/p/chromium/issues/detail?id=315190 https://s3.amazonaws.com/chromebugs/memory.html https://s3.amazonaws.com/chromebugs/memory.html
- myfonj 8y ago
  Whoa, that page crashed my (long running) Nightly (presumably exhausted RAM completely) and in freshly started got 4 GB for the tab process (and survived). Nice.
reitanqild 8y ago
> If anyone runs into problems like this, feel free to bug one of the Chrome dev rel folks, such as me. Hi, and thanks for being part of creating Chrome && reaching out here. Now that I have a Chrome guy here maybe you can help with another annoying issues: -QC internally at Google seems to be blissfully unaware of the fact that other browsers exists. Examples: - one glaring issue I'm running into in core Angular on a daily basis. - Google Calendar performance is sometimes unreasonably slow in Firefox - For weeks or months Google search results would drive once CPU core to 100% twice a minute.
- notatoad 8y ago
  none of those are something a chrome dev rel person can help you with. People like you are the reason we have to deal with three layers of low-level tech support before we can actually talk to somebody who knows what they're doing - please don't just spray your random complaints at anybody who happens to be related to google in any way.
  - gsnedders 8y ago
    And it's not like the Chrome dev rel team doesn't fight for these things, but ultimately the Chrome team doesn't have any control of prioritisation of bugs in other products (like Calendar). The only way we're going to see a significant change is when those high up in the Google org chart start caring about products working well in other browsers; as long as it's up to each individual product we'll continue to see products prioritising time-to-market and targeting only the browser with the majority of the market.
    - reitanqild 8y ago
      That's the second reason to post it here: because if you see one googler there are hundreds nearby, and some of them might be at the relevant team. (And if I point out often enough what happened last time a mega corp abused their position to market their browser then maybe some of them starts talking about it internally?)
  - 8y ago

robotmlg 8y ago

Did you report the Safari bug to Apple or to WebKit.org? I've had good luck getting responses and fixes from the webkit guys

Rodd45 8y ago
They seem to get the things done professionally and effectively.

CryoLogic 8y ago

I reported a very serious one to Edge recently and the team told me they would "backlog it and might be on a future release". Chrome had already patched it and Firefox never had it. (It was related to incorrect DOM spec implementation of document inheritance allowing cookie access from anywhere). I'll do a full write up and blog it when I'm back from vacation but to summarize I was really unimpressed by the team at Edge and Microsoft Security.

driverdan 8y ago

Did you include a 90 day public disclosure window?

deleted 8y ago

[deleted]

robocat 8y ago

Personally over many bug reports and many years: A+ experience with the Chrome team E with Edge F with Safari The Chrome devs have been astonishingly good. My experience has repeatably been that if they are given a good bug report, they get it fixed and often fix it really fast. Or they reply with excellent technical reasons why not. Also multiple times I have seen extreme corner-case regressions get magically fixed without me reporting anything! Edge - always waffle and misdirection in reply to bug reports. I only bother to give them very well documented, repeatable bugs, plus attached repro file, for things I really need fixed. However: I did have one good experience recently because I reported the bug for the Edge beta, on a feature they were actively working on catching up to the other browsers (however they still had poor interaction). Safari: hopeless. Report a critical bug with excellent repro file, and get no response, and no fix. No rating for Firefox because I haven't bothered reported any bugs to them in the last few years. Edit: this is for non-security related bugs.

odbol 8y ago
Apple hears ya, Apple don't care.
- masklinn 8y ago
  Yeah apparently from people familiar with the deep black hole that is Radar you're supposed to keep submitting bugs, dupes count as a vote or something. It sounds absolutely horrendous.
ikeboy 8y ago
I once reported a chrome issue. Got no attention until I found a different issue I thought was related and commented there, which got the attention of someone competent who realized it was a hardware bug they'd fixed before but had a regression. Not a security bug, just that a very large number of websites didn't load.

userbinator 8y ago

In other words, the experience gets progressively worse the bigger the company. I'm not surprised, having worked in companies of that scale the amount of bureaucracy and general red-tape to do the smallest of things is absolutely irritating.

mito88 8y ago

and Samsung's browser?