rickmans wrote:Arguments to keep it the old-fashioned way are as valid as changing them with the only difference there were not (that many) users that would like to change the original behaviour (at least I did not found that many entries in bugzilla)
While convenient to you, the "old-fashioned way" is flat-out broken for a different group of keyboard users whereas the new behavior is just inconvenient. "Broken" vs "inconvenient" isn't really what I'd call "as valid".
rickmans wrote:You offered a default that is different from the last view years and different from most browsers.
Please don't say "most browsers" when you actually mean "Internet Explorer". Otherwise let me repeat: most browsers have their own solution (from the top of my mind: Ctrl, Ctrl+release, Shift+Esc, Alt -- and now Alt+Shift/Ctrl+Shift/Ctrl [depending on the OS]). Even when restricted to Windows, you'll still get Alt and Shift+Esc (you might find this thread interesting as for why Opera doesn't use Alt).
rickmans wrote:Depending on an extension is like saying: "we know it sucks, but probably someone else will also think it sucks and he will fix it".
Nobody depends on an extension but those wishing the good ol' days back, so it's rather like saying "we know not everybody will be happy and thus we'll allow for a pretty simple fix".
rickmans wrote:As you already said in this thread: you probably have got some statistics to share in order to prove your point. .
I didn't mean to make any comparison by number. I rather wanted to point out that the choice between breaking the browser for one group and making it slightly less convenient for another shouldn't really be too difficult to make.
rickmans wrote:Do you really want to have a lot of forum users which can not post by default in the way they are doing for the last 5 years (with alt+s).
Please specify "a lot of" without just using plain old browser statistics -- these simply don't tell how many of those users have actually been using Alt+S at all.
rickmans wrote:Why not not fixing that bug and wait for an extension for that option? .
Because the fix had to be at the very core of Firefox which is highly non-trivial to affect by extensions (if possible at all). Now an extension can make a difference, before it simply couldn't...