4 ms·
The cynic in me thinks this just happened because of a code rewrite they wanted to do anyway for reasons unrelated to this bug report. It’s just a coincidence t
by pwdisswordfish8 5y ago
The cynic in me thinks this just happened because of a code rewrite they wanted to do anyway for reasons unrelated to this bug report. It’s just a coincidence that the rewrite allowed them to close it. (The initial report mentioned XUL, which if I understand correctly, isn’t even used in Firefox any more.) This is hardly some kind of a commendable instance of listening to your users.
I mean, compare it to this bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=309807 https://bugzilla.mozilla.org/show_bug.cgi?id=309807
First the response was ‘just use an extension’. I did that happily, until the extension API was neutered, making the extension non-functional. When people brought that up, Mozilla closed comments on the bug report. Now it is closed as WONTFIX with this laughable excuse:
> Extension APIs (which I know aren't yet available) would be the solution for implementing this if there is enough demand.
Meanwhile, Chromium had this from day one. It works a bit differently now, but it’s still there, I just checked. Doable? Perfectly doable.