Linked by Thom Holwerda on Wed 25th Aug 2010 19:21 UTC
Mozilla & Gecko clones Today, Mozilla released the fourth beta of Firefox 4.0. After a period of what I would call stagnation, the Mozilla team are back on track with delivering interesting UI concepts. They were sensible enough to copy Chrome's excellent tabs-on-top UI, but have now also added something called Panorama, a new and very interesting way of managing your open tabs.
Thread beginning with comment 438310
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Kroc
by Beta on Thu 26th Aug 2010 12:28 UTC in reply to "Comment by Kroc"
Beta
Member since:
2005-07-06

How about they fix those 10 year old CSS bugs instead of piling in more bloat and bling.

Some bugs are expensive to fix with regards to time, with little obvious gains. How should they balance developer time between that and implementing HTML5?
Some CSS features are behind (like overflow: ellipsis), but I understand their rational in bug comments…

Mozilla have lost the plot. The Firefox brand has become more important to them than actual users.


Did anyone using Chrome bitch this much about missing MathML support before it appeared? No… I think you’re being rather harsh on Mozilla. They’ve got people playing in the interface as well as all the developers they had previously working on Gecko.

Reply Parent Score: 5

RE[2]: Comment by Kroc
by Kroc on Thu 26th Aug 2010 15:29 in reply to "RE: Comment by Kroc"
Kroc Member since:
2005-11-10

As DeathShadow said above, in open source nobody wants to do the grunt work. There’s a reason why IE has the only full implementation of CSS 2.1, they paid their developers to the do it. A broken implementation is worthless and negatively effects everybody—100% complete, or not at all. Microsoft saw the importance of getting CSS2.1 done-and-dusted before working on HTML5. How am I supposed to have faith in Mozilla to implement HTML5 when they can’t even finish a ten year old job?

I can’t count the number of websites where #915 would have made a *big* difference to me, but Mozilla call it irrelevant because it’s old and unused *BECAUSE THEY MADE IT RARE AND UNUSED BY NOT IMPLEMENTING IT*. A self-fulfilling arsehole weasel get out—don’t implement something so developers can’t demonstrate practical uses, and then claim the feature isn’t needed anyway anymore and nobody will miss it.

Reply Parent Score: 2

RE[3]: Comment by Kroc
by daveak on Thu 26th Aug 2010 18:44 in reply to "RE[2]: Comment by Kroc"
daveak Member since:
2008-12-29

There was me thinking the only reason was that all the stuff that wasn't implemented from 2.0 or was implemented incorrectly was dropped or re-speced to do what browsers chose to do instead of following the spec. (This comment applies to all browsers, not just IE). How to gain compliance 101. Redefine the specifications.

I will also question, but I'm not sure, as to whether they have a full implementation, or if as with CSS 1.0 they claim to have a full implementation but only support mandated sections and not optional parts.

Reply Parent Score: 1