So would anyone in the business, but that never was the case. This one was just a simple css coding job and Dao (one of the main Mozilla devs) saw it as such. But no, it had to be the usual Mozilla stuff of decide first, then hunt around for a reason, then spend ages justifying it...and then being defensive.arturox wrote:Thanks James for the answer to my question... A double code stack relating to tabs is difficult to maintain... That I understand.
Mozilla are actually very good at being defensive, which is fine but this is the major Open Source browser out there. So, if Firefox is not going to look after the needs of minorities, then who is?
For example, the needs of children, special needs and the aged forgetful were being met by 'Icons with Text' and 'Text Only' modes, so 5 years back Mozilla removed them. Where was the mythical triple code stack then, considering the code is still in there 5 years later and can be brought back to life with userChrome.css? That removal wasn't a business decision, that was downright nastiness.
This is the reality of it all - the original Bug Report - before the spinning started.