4 ms·

For Firefox, that's really not sufficient. I've reported FF bugs in the past that sit unfixed in the queue for 13 years. It has disincentivized me from botherin

For Firefox, that's really not sufficient. I've reported FF bugs in the past that sit unfixed in the queue for 13 years. It has disincentivized me from bothering to continue reporting them. Yes, it's open-source and I could in theory pop it out and fix it myself (ha, because I have a spare weekend to burn on setting up a Mozilla dev environment and dependency stack). No, there's no incentive to do so when Chrome simply doesn't have the bug. Chrome has bugs that languish too, but so far I can't name any that I've tripped over. I'm sure when I do, it'll be incentive to consider switching to Firefox.

gcb0 10y ago
and when you trip on that chrome bug you will move to what? IE? btw, try to disable referrer on chrome ;) ... or even set it to only send to the same domain
- fixermark 10y ago
  As I said, it'd be incentive to switch to Firefox (or actually set up that Mozilla devel dependency stack and fix the 13-yaer-old bug). For referrer in Chromium, I think there's a flag? https://cs.chromium.org/chromium/src/content/public/common/content_switches.cc?q=no-referrer+flag&sq=package:chromium&l=660&dr=C https://cs.chromium.org/chromium/src/content/public/common/c...