2005
4
Jun
4
Jun
As the title says, Acid2 is now passed.
With the help of Hyatt's Safari patches, Ivor Hewitt(*) and I have finally made Konqueror pass Acid2 as only the second browser.
Roughly half of the Safari Acid2 patches could be merged in some form or another, and another two bugfixes could be merged from Safari 1.3 once found and isolated. The rest was written from scratch. All in all not a bad reuse of code, allthough slow.
The fixes are at the moment in KDE 3.5 branch, but will soon be merged into KDE4, and evaluated for KDE 3.4.2 inclusion.
(*) Ivor is a new KHTML developer, and author of the adblock feature.
- carewolf's blog
- Login or register to post comments
- 6196 reads
Syndicate Blogs
Comments
Reusing blocs of code can
Reusing blocs of code can sometimes take up more time. I prefer to restart typing a new program. Sometimes I find better ways to get where I want, ways I'd ignore if I reused the same code.
---
Mary-Anne Davis, programare iasi affiliate.
very good
long waited, thanks
Great and unbelievable!)As
Great and unbelievable!)
As far as i know for a long while the only browser that passed Acid2 test was Safari.
Amazing
I will try this browser... I loved safari so it may be useful for me too..
regards, topanga
Acid test
When taking the test, you should use the default settings of the browser you are testing. Changing the zoom level, minimum font size, applying a fit-to-width algorithm, or making other changes may alter the rendition of the Acid2 page without this constituting a failure in compliance.
Konqueror bug open since ages: "WEB.DE jump html fails"
Alan,
as my bugreport never has been answered, I try it here:
Can you investigate into this bug?
https://bugs.kde.org/show_bug.cgi?id=85010
a) It can easily be reproduced
b) It is a open Konqueror bug since KDE 3.2.2 (or earlier?)
I want to help fixing the bug, but am not a programmer.
Regards,
- When taking the test, you
- When taking the test, you should use the default settings of the browser you are testing. Changing the zoom level, minimum font size, applying a fit-to-width algorithm, or making other changes may alter the rendition of the Acid2 page without this constituting a failure in compliance...
Just cup of beer 4 you. Cheers!
How's that working for you?
Is this going to become a regular way to draw attention to particular bugs?
If so, then here's one that could use some :)
http://bugs.kde.org/show_bug.cgi?id=113728
safari passes acid2 test??
so... is the version of safari that comes with tiger supposed to pass the acid2 test?? cause i was at my friends house earlier, and i tested the link shown on that screenshot, and apparently.. the version of safari he had (2.0; default tiger install i think), didn't render the image properly.
* As of December 11, 2006,
* As of December 11, 2006, the nightly builds of Mozilla line of browsers (Firefox, Camino, SeaMonkey)
Although the Web Standards Project web site states that iCab passes Acid2, it technically falls short by displaying a scrollbar on the viewport. (A correctly rendered test should not have a scrollbar.[4]) This has since been fixed with the release of iCab 3.0.3. Konqueror originally had the same problem when it first was stated to have passed the test, but this issue was corrected with release 3.5.2.