[horza]

Autor gog

?!?!?!? Da nisi malo pobrkao lončiće i zamijenio Operu i IE?

Opera prolazi Acid2 test koji još uvijek ni najnovija inačica Firefoxa ne prolazi.

http://www.webdevout.net/browser-support-summary

nisam ja niš pobrko
postoji samo jedan task force za standardizaciju www-a. to je http://www.w3.org
A svi ostali se mogu sakriti sa svojim bijednim pokušajima dobivanja kredibiliteta neinteligentnim testovima. Dovoljno o meritornosti acid2 testa govori:
http://jigsaw.w3.org/css-validator/v...d2%2Ftest.html

btw

Understand this page before you link to it or quote it:HTML, CSS, DOM, and ECMAScript support tables. Every feature with bugs is treated equally in the calculation, regardless of the subjective real-world severity or number of perceivably distinct bugs with that particular feature. These tables attempt to detail every case in which the browser conflicts with the standard, so some of these bugs that have relatively little real-world severity, such as the handling of some illegal CSS property values, are calculated with the same significance as nearly unsupported values. Doing otherwise would introduce subjectivity and bias, which this resource attempts to avoid. As a result, these percentages should only be regarded as general ballpark figures. These percentages are derived from the feature-by-feature testing in the

i što sami kažu o specifikaciji svojih testova... btw, oni testiraju prema W3C-ovim CR specifikacijama. ja fakin ne želim imati browser koji radi prema CR specifikacijama. to bi ga i učinilo non-standard-compliant. điiiz. bljuuuuv

World Wide Web Consortium specifications are included in this resource once they have reached the Candidate Recommendation (CR) status for the first time. Some of the technologies detailed here, such as the changes in CSS 2.1 over CSS 2 and the included sections of CSS 3, are still at this stage or have been regressed from CR status. This means that these technologies are not yet technically considered web standards and it is incorrect for these new features to be used on webpages. The CR stage is when web browsers are expected to begin implementing support for the relevant features. After the specification is implemented by a predetermined number of user agents, it moves on to Proposed Recommendation status and eventually becomes a Recommendation. It isn't until a specification reaches this Recommendation stage that it is technically considered a web standard. For more information, see Advancing a Technical Report to Recommendation.