Linked by David Adams on Tue 23rd Sep 2008 00:57 UTC
From eWeek: "In a session billed as the browser wars up close and personal, key Microsoft, Mozilla and Google representatives spoke about the past present and future of the browser platform as they see it . . . one of the issues that stood out to me was that of developer discontent. When the Ajaxians opened up questioning to the audience, an attendee stood up and said Google's announcement of its new browser "was greeted with shock and horror," by him."
Thread beginning with comment 331103
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Javascript acid test?
by sbergman27 on Tue 23rd Sep 2008 07:12
in reply to "Javascript acid test?"
Member since:2005-07-24
That would be Acid 3, of course. Epiphany with Gecko 1.9 gets 71/100. Epiphany with Webkit gets 97/100. I think I heard the IE8 beta 2 score is something like 17/100. You are quite correct in pointing out that javascript compatibility is the big hurdle for web apps. (And even just web sites.) Incompatible CSS behavior makes the site look odd. Incompatible javascript behavior completely breaks the site, making it unusable. Mozilla and Microsoft really need to get with the program.
Edited 2008-09-23 07:19 UTC
RE[2]: Javascript acid test?
by nxsty on Tue 23rd Sep 2008 09:12
in reply to "RE: Javascript acid test?"
Member since:2005-11-12
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2007-03-04
Seems like a Javascript acid test is necessary, to have the same JS behavior across browsers, like there is for HTML and CSS. Imagine a JS acid test that would use all JS functions and behaviors one after the other. Hum...
I read "Google Talk" in the title and I wondered why