Safari Passes the Acid2 Test 430
TigerX writes "The Mac web browser Safari has become the first browser to pass the Acid2 test. Acid2 is a CSS/HTML test suite put out by the Web Standards Project (WASP). Developer David Hyatt had been working on the project for the past few weeks. Details can be found at his blog. The patched Safari is not yet avaliable for public consumption. It is unknown when the patches will appear in a public version of Safari."
KHTML (Score:4, Informative)
I hope these fixes trickle back down to KHTML soon. In time for KDE 3.5 would be great.
Re:Firefox? (Score:4, Informative)
Re:Purpose of Acid2 (Score:5, Informative)
Acid2 is a test page for web browsers published by The Web Standards Project (WaSP). It has been written to help browser vendors make sure their products correctly support features that web designers would like to use. These features are part of existing standards but haven't been interoperably supported by major browsers. Acid2 tries to change this by challenging browsers to render Acid2 correctly before shipping.
Acid2 is a complex web page. It uses features that are not in common use yet, because of lack of support, and it crams many tests into one page. The aim has been to make it simple for developers and users to check if a browser passes the test. If it does, the smiley face on the left will appear. If something is wrong, the face will be distorted and/or shown partly in red.
The purpose of this document is to explain how Acid2 works. The markup behind Acid2 is peculiar in that it attempts, on one single page, to test many different features. We do not envision or recommend that normal Web pages should be written this way, but it is appropriate for a test page. At first sight, the source code is hard to understand, but the guided tour offered in this document will explain it in some detail. The guide assumes a technical understanding of HTML, CSS and PNG.
Re:Purpose of Acid2 (Score:5, Informative)
Basicaly the point being not in obscure code , but in rendering normal code properly
Web designers/developers will use the code when it is avaliable in their arsenal.
As of now , the newest version of webcore is the only rendering engine that can do it so congratulations to apple(and ofcourse the khtml team
Re:Konqueror? (Score:3, Informative)
Sweet baby Jesus in a car seat... (Score:5, Informative)
The term "acid test" dates back to the freaking gold rush days when they would use nitric acid to test for gold.
Re:Safari was already pretty nice, thanks. (Score:4, Informative)
Change the entry "when you insert a music CD open iTunes" to your favourite app. Bob's your uncle.
Good luck finding something better than itunes by the way.
Re:Hmmm (Score:5, Informative)
There is where the "quirks mode" [mozilla.org] comes in. The browser should (and is) able to detect whenever something is written after the standard, or not. If it is written in a standard compliant manner, it should be rendered the same everywhere. If it is in quirks mode, it should be rendered different, and the page will behave different.
Re:Go Apple! (Score:2, Informative)
Re:Go Apple! (Score:3, Informative)
Re:Go Apple! (Score:5, Informative)
Yes, the same "schmoe" who happens to be the development lead for the Safari project. Seeing as how he works for Apple, it would most certainly be Apple who did this.
Re:Safari was already pretty nice, thanks. (Score:3, Informative)
Re:Go Apple! (Score:5, Informative)
http://validator.w3.org/check?uri=www.slashdot.or
Neither, and both. (Score:3, Informative)
The patches are actually to WebKit, which is the actual GUI component that renders the HTML. Both browsers (Safari and Safari RSS) actually use the same rendering component IIRC. As does any other of the zillion of apps on the system that embeds the webkit framework to render HTML.
Of course, the actual changes are in neither version yet. They're still in the development version. We'll have to wait for some apple updates to see the changes.
Me? I'm more interested as a programmer in getting the documentation for the cool new features in the latest version of WekKit that's just been released (and described further down in the blog.)
Re:More to the point (Score:3, Informative)
Re:so does opera (Score:2, Informative)
Re:More to the point (Score:2, Informative)
I don't get what all the fuss is about -- doesn't everyone with sufficient interest in this issue to read the story know that Apple has been sharing patches (and KDE has been using them) for two years?
Re:Go Apple! (Score:5, Informative)
Comment removed (Score:5, Informative)
Re:so does opera (Score:5, Informative)
Re:The acid2 test doesn't use valid CSS... (Score:4, Informative)
From WASP website (Score:5, Informative)
Transparent PNGs -- The eyes are encoded as transparent PNGs.
The object element -- The eyes of the face are attached to an object element. Being able to use object (which can have alternative content) is one of the oldest requests from web designers.
Absolute, relative and fixed positioning -- Being able to position elements accurately is important for advanced page layouts.
Box model -- The original Acid test focused on the CSS box model. Acid2 continues in this fine tradition by testing 'height', 'width', 'max-width', 'min-width', 'max-height' and 'min-height'.
CSS tables -- There is nothing wrong with table layouts. It is a powerful layout model which makes sense on bigger screens. However, the table markup is troublesome as it ties the content to these screens. Therefore, being able to specify table layouts in CSS is important.
Margins -- CSS defines accurate algorithms for how margins around elements should be calculated.
Generated content -- The ability to add decorations and annotations to Web pages without modifying the markup has long been requested by authors.
CSS parsing -- Acid2 includes a number of illegal CSS statements that should be ignored by a compliant browser.
Paint order -- We test that overlapping content is painted in the right order. This is not a feature in itself, but a requirement for other features to work correctly.
Line heights -- The Acid2 test checks a few key parts of the CSS inline box model, upon which any standards-compliant Web page depends.
Hovering effects -- One of the elements in the face changes color when you hover over it. Which one?
Re:Sweet baby Jesus in a car seat... (Score:2, Informative)
Your point?
Re:The acid2 test doesn't use valid CSS... (Score:3, Informative)
Re:The acid2 test doesn't use valid CSS... (Score:3, Informative)
This page states that:
"Acid2 includes a number of illegal CSS statements that should be ignored by a compliant browser."
Re:What is it supposed to test ? (Score:3, Informative)
Acid2 page is not supposed to validate because it tests both compliance with how things should be rendered and with what shouldn't be rendered at all.
Re:Firefox Results (Score:5, Informative)
Sadly, Acid2 won't be high priority before Gecko 1.9, which means that firefox won't be fully CSS2 compliant before at least version 1.2.
Re:Passed test but not available? (Score:3, Informative)
In-Brain Parser. In other words they didn't. In fact there was a bug in the test that Dave Hyatt found by implementing a compliant browser! The ACID2 Test is now at version 1.1 to reflect that bug fix!
Re:Another reason why open source is good (Score:5, Informative)
Re:Tiger or Panther? (Score:3, Informative)
It's avaible to Konqueror users though, of course, if they can go through applying the patch to the KHTML engine's source and recompile (or they'll just wait for the next Konqueror version that'll implement these patches)
Re:But will they share? (Score:2, Informative)
This code is in the WebCore which is one of Apple's Open Source projects.
Check it out here [apple.com].
So if the KHTML team wants to put this code in the main khtml tree they can. Since Apple's Open Source License is GPL compatable
Re:But will they share? (Score:3, Informative)
Re:CSS (Score:3, Informative)
Re:Go Apple! (Score:5, Informative)
CSS parsers are designed to degrade when they come across things they don't recognise; that's what it's testing.
Re:Go Apple! (Score:5, Informative)
Re:Another reason why open source is good (Score:4, Informative)
This is the exact same thing that happened way back when - when safari was first unveiled. Apple submitted a large tar, and then helped the KHTML team decifer it.
Being both a Safari *and* Konq user, this makes me happy.
Suggestion: know what you link
Re:Go Apple! (Score:5, Informative)
Re:Yes, but... (Score:3, Informative)
Re:Go Apple! (Score:2, Informative)
Re:Yes, but... (Score:1, Informative)
Re:Tiger or Panther? (Score:4, Informative)
Re:Yes, but... (Score:5, Informative)
http://weblogs.mozillazine.org/hyatt/archives/200
Re:Yes, but... (Score:5, Informative)
Although it doesn't seem to be very useful [kdedevelopers.org].
Re:More to the point (Score:5, Informative)
Zack Rusin just blogged about this [kdedevelopers.org].
Re:Another reason why open source is good (Score:1, Informative)
How about a blog from today? [kdedevelopers.org]
Apple == not quite so helpful to KDE (Score:2, Informative)
Umm, not quite. Pointing towards a link made by someone ealier here [kdedevelopers.org]:
We created the khtml-cvs list for Apple, they got CVS accounts for KDE CVS. What did we get? We get periodical code bombs in the form of them releasing WebCore. Many of us wanted to even sign NDA's with Apple to at least get access to the history of their internal vcs and be able to be merging the changes incrementally, the way they can right now. Nothing came out of it. They do the very, very minimum required by LGPL.
And you know what? That's their right. They made a conscious decision about not working with KDE developers. All I'm asking for is that all the clueless people stop talking about the cooperation between Safari/Konqueror developers and how great it is. There's absolutely nothing great about it. In fact "it" doesn't exist. Maybe for Apple - at the very least for their marketing people. Clear?
Don't believe everything Steve Jobs tells you, so to speak.
Re:But will they share? (Score:4, Informative)
Argh. I thought I hit Extrans. (Score:5, Informative)
"Do you have any idea how hard it is to be merging between two totally different trees when one of them doesn't have any history? That's the situation KDE is in. We created the khtml-cvs list for Apple, they got CVS accounts for KDE CVS. What did we get? We get periodical code bombs in the form of them releasing WebCore. Many of us wanted to even sign NDA's with Apple to at least get access to the history of their internal vcs and be able to be merging the changes incrementally, the way they can right now. Nothing came out of it. They do the very, very minimum required by LGPL."
Go read the whole post. Very informative, and kind of sad.
Konqueror (Score:3, Informative)
Re:Go Apple! (Score:2, Informative)
Apple droids are far worse than even Linux droids - I see that my completely factual, sober post was marked a "troll" by one wanker, in the same way that a bunch of Apple apologists stormed the prior discussion about Apple strong-arming a book publisher. What a sad, sad bunch.