p2pnet - rss feed: WaSP comes the new acid
p2pnet.net News:- WaSP says its new Acid2, meant to exposing flaws in the implementation of “mature” Web standards, has already found flaws in all tested browsers including Internet Explorer, Firefox, Opera, and Safari.
WaSP is short for Web Standards Project and, "We are actively encouraging makers of Web design tools to use Acid2," said Drew McLellan of its Dreamweaver Task Force.
"Any tool that uses WYSIWYG needs to pass the test to offer an accurate representation of how the page will look in a compliant browser."
The organization says it’s also actively inviting feedback.
Go here to take the Acid2 test.
Something you think we should know? tips[at]p2pnet.net
April 18th, 2005 at 11:03 pm
I am not sure what the test is and what its contents are for getting WYSIWYG. I am sure that Microsucks has purposely setup a browser full of holes for the functioning of business. Otherwise many spywares would not work were it their intention to make a safe browser. As it is, Microsucks sees problems as being user problems till either it can’t be hid or till they eventually get around to it. There are several organizations that have at one time or another made special note to Microsucks of security problems with both its OS and its browser and a year later it was still ignored.
A good example of one where it could not be ignored was when the Homeland Security office issued a special warning to consumers to get rid of the security problem of Internet Explorer in favor of a more secure browser such as Firefox or Opera. If meeting this WYSIWYG means a less secure browser, I can live with the lack of it meeting certain standards. What resulted when Microsucks rushed to fix the issue was SP2. The speed at which it got out left it without being tested on many systems for compatibilty. The horror stories of folks fighting with a partial install that went wrong were legend.
April 19th, 2005 at 7:09 am
All “other” browser makers, that means Opera, Mozilla and Apple are actively fixing Acid2 as we speak.
Opera employ the guy hat made Acid2, and he is in contact with Mozilla and Safari dev’s hammering out the bugs which cause imperfect rendering of Acid2.
Opera have just released Opera 8[1] without fixes, but this is because they froze their code just when Acid2 was released.
So we know all browsers will fix Acid2 soon, the question is what will microsoft do…
—-
[1] not official yet - see the wiki: http://nontroppo.org/wiki/Opera