Making Firefox consistent across platforms has always been secondary to making it consistent with per-platform guidelines. We don't always do a good job of this, but that's how it is, and rightly so. Consistency across browsers is also secondary.
> This isn't at all a GNOME-vs-KDE-vs-Windows issue, it's
> a basic usability issue
Indeed, and the issue is that "backspace == back in history" can lead to irreversible data loss and is relatively easy to trigger by mistake. These are the principles behind the decision.
> The majority of GNOME users (let alone users of other
> desktop environments) don't want this. That's the
> bottom line.
You have no way of knowing this, since you have not surveyed them in a statistically valid way.
The people who complain about backspace == back in history can be found here: /bugzilla. mozilla. org/show_ bug.cgi? id=262905
https:/
I did ask people to look in related bugs before commenting.
Making Firefox consistent across platforms has always been secondary to making it consistent with per-platform guidelines. We don't always do a good job of this, but that's how it is, and rightly so. Consistency across browsers is also secondary.
> This isn't at all a GNOME-vs- KDE-vs- Windows issue, it's
> a basic usability issue
Indeed, and the issue is that "backspace == back in history" can lead to irreversible data loss and is relatively easy to trigger by mistake. These are the principles behind the decision.
> The majority of GNOME users (let alone users of other
> desktop environments) don't want this. That's the
> bottom line.
You have no way of knowing this, since you have not surveyed them in a statistically valid way.