PUBLIC MARKS with tag QA

Yet, these 16 chars cost around 1200$* in direct labour time and 3 engineers were involved.

We're not planning to cram a bunch of Fixes into Firefox 3 since it's almost ready, and cramming features in at the last minute risks hurting other Web standards support or hurting some of the other things that make Firefox a great browser.

oui. un discours réaliste (bien que nouveau) qui prend en compte tout le contexte. Cela me rappelle une anecdote d'une amie. Au Canada, elle pratiquait le karaté. À la fin de chaque année, elle était préparée pour passer l'examen des ceintures. Au Japon, elle a repris les cours à zéro. Le maître propose enseigne la technique et la philosophie du karaté et les individus ne se présentent à l'examen que quand ils sont prêts. C'est toute la différence entre passer le test Acid 3 avec hack ou pas, et implémenter sérieusement la technologie en étant sur de ce que l'on fait. Et je trouve, dans ce cas ci, la démarche de Mozilla et son changement de discours plutôt bien.

Regarder les communautés évoluer est toujours intéressant. Que ce soit celles du w3c ou ailleurs. Complexe. Y participer, c'est accepté d'avoir les mains sales ou alors on est un sombre ignare idéaliste.

Probably the best-known strictness disaster is HTML. […]

Some people argue that HTML is commonly used because it’s not strict. That the non-strictness of its design makes it popular. That if web browsers had always just thrown an error instead of accepting invalid HTML, somehow people would not have used HTML. That is a patently ridiculous argument.

The point is that JavaScript developers shouldn’t have to detect and workaround such issues. JavaScript should work the same across all implementations. We believe this is the first step in making JavaScript better. To make it possible to achieve such implementation conformance, the first step is knowing where the divergences are. We in the JScript team are looking into where various browser based implementations diverge, where our engine is incorrect in its interpretation of the specification, what if any de facto compatibility conventions have been reached, and the value of codifying such conventions into the standard. We’ve published the first draft of JScript Deviations from ES3 as a starting point.

Full spec support by 2010 I will no longer compensate for limited or broken specification support in browsers after January 1, 2010. This gives IE, and the other browsers, time to fully implement all of the specifications that have been out as recommendations for years now. This includes support for XHTML 1.1, CSS 2.1, SVG 1.1, in addition to any other specification not listed. This isn't part of a movement, and there is no badge. This is just my personal choice that I will no longer compensate for browsers not implementing standards, beginning January 1, 2010.

I’ve already stopped using ems as a relative unit for layout and sizing and have gone back to pixels because of the zoom for IE7 that works like Opera.

# The lines output by Curly Logo weren’t being broken, everything was stuck together on one line. Turns out Firefox was letting me get away with creating (XHTML) p nodes by using “document.createElement” whereas I should really be using the XML approved “document.createElementNS” to create nodes from the XHTML namespace. So now I do.

Validate on an airplane or the subway - no network needed.