Linked by Thom Holwerda on Wed 25th Aug 2010 19:21 UTC
Permalink for comment 438333
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
More News »
Sponsored Links



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.