Firefox fails to properly render http://acid3.acidtests.org/

[ethana2]

Binary package hint: firefox-3.0

It is important for the future of the web that Firefox handles the following page perfectly before 3.0 is released:
http://acid3.acidtests.org/
The correct rendering of this page is shown here:
http://acid3.acidtests.org/reference.

It is through universal and strict web standards compliance that gecko, webkit, and opera will evict Internet Explorer from its much abused position of dominant market share. The less quirks a browser engine has to be able to handle, the smaller and cleaner its code base can be.

Passing ACID3 would be a fine milestone for this major release.

---------------------
Not displaying correctly?
This site is best viewed with Firefox 3 or other standards compliant browser.

ProblemType: Bug
Architecture: i386
Date: Fri Feb 29 19:15:29 2008
Dependencies:

DistroRelease: Ubuntu 8.04
Package: firefox None [modified: /var/lib/dpkg/info/firefox.list]
PackageArchitecture: all
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-10-generic i686

[Jwalden+bmo (jwalden+bmo)]

This is probably easiest to track in a spreadsheet. I started one to deal with
the individual tests in this:

http://spreadsheets.google.com/pub?key=pNgBCwWdyRTT2JeiZn4B2Yw

A link to edit it's at the bottom of the page. Currently Gavin and I have edit
access; ask him if you want to be able to edit it.

[Sylvain Pasche (sylvain-pasche)]

Can you give me access?

Tests 4 up to 8 are bug 132824

[Jwalden+bmo (jwalden+bmo)]

It's not obvious, but clicking on the "Acid3" title will alert a list of the tests that failed.

[Asrail (asrail)]

It's in the comments but it's worth to put here:
click on the "A" of the title - no other letter will give you the list.

Shift-click the "A" to get the report on the current page, instead of an alert.

[Arpad Borsos (swatinem)]

Can someone with the appropriate rights please add Bug 73586 – matching of :first-child, :only-child, and :last-child not dynamically updated [SELECTORS-DYNAMIC] to the dependencies?
Tests 35-37 fail due to that bug.

[Mp3geek (mp3geek)]

With acid3, the browser locks up for a bit on the 14% before continuing. is this a javascript bug?

[Jwalden+bmo (jwalden+bmo)]

It's some inefficiency (specific area of functionality not currently known) as acid3 does its best to force a garbage collection; I suspect it'll get improved some with the current and ongoing perf work. However, I personally doubt it'll get a *huge* amount of specific attention in the immediate future, at least until the low-hanging fruit (of which there's still plenty, in my estimation) in acid3 is fixed, as no real-world page is actually going to do what's being done there.

Also, given the current point in the release cycle, acid3 is extremely unlikely to be fixed in Firefox 3, so nobody who hacks on Firefox full-time is likely to spend much time on it now, except coincidentally.

[Bzmozilla (bzmozilla)]

Tests 26,27 and 73 appear to pass...

[cubeeggs (rlanday)]

26 and 27 are passing for me, but not 73.

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b3pre) Gecko/2008013104 Minefield/3.0b3pre

[Jwalden+bmo (jwalden+bmo)]

26/27 don't pass when I run them. The reason people are reporting different things is that the test basically relies on a garbage collection happening, but I think that behavior's going to be system-dependent to an extent, and it might just be that some systems don't GC in the right period of time.

I also see 73 passing; for now I've marked it as a yellow PASS that we can revisit later to figure out what's up.

[Aja+bugzilla (aja+bugzilla)]

New URL for the "final": http://acid3.acidtests.org/
per http://www.css3.info/acid3-completed/

Acid and Acid2 are hosted there now, too.

[Jwalden+bmo (jwalden+bmo)]

(In reply to comment #11)
> per http://www.css3.info/acid3-completed/

Sure. Note, however, that despite what the site says, acid3 isn't yet completed, and it's still changing for a little while longer.

[cubeeggs (rlanday)]

Booted off of a drive with Tiger on it, (Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3pre) Gecko/2008020204 Minefield/3.0b3pre), I get the opposite of what I had before: 26 and 27 failing, 73 passing. Is there a chance this is a Tiger/Leopard issue?

[Matthew-matthewhutton (matthew-matthewhutton)]

FWIW Test 26/27 fail and 73 passes with Webkit r30377 on Intel Leopard, so it looks likely to be a Firefox Issue

[Mp3geek (mp3geek)]

Just wondering why the windows builds are currently at 66/100, and my newly compiled linux build is at 65/100, why would there be a difference?

[Crazy-daniel (crazy-daniel)]

Even on Windows there's sometimes a difference of 1 point. Last week I noticed test #80 somtimes failed and sometimes did not fail. However, it looks like this test was changed recently as well.

[ethana2 (ethana2)]

Binary package hint: firefox-3.0

It is important for the future of the web that Firefox handles the following page perfectly before 3.0 is released:
http://acid3.acidtests.org/
The correct rendering of this page is shown here:
http://acid3.acidtests.org/reference.

It is through universal and strict web standards compliance that gecko, webkit, and opera will evict Internet Explorer from its much abused position of dominant market share. The less quirks a browser engine has to be able to handle, the smaller and cleaner its code base can be.

Passing ACID3 would be a fine milestone for this major release.

---------------------
Not displaying correctly?
This site is best viewed with Firefox 3 or other standards compliant browser.

ProblemType: Bug
Architecture: i386
Date: Fri Feb 29 19:15:29 2008
Dependencies:

DistroRelease: Ubuntu 8.04
Package: firefox None [modified: /var/lib/dpkg/info/firefox.list]
PackageArchitecture: all
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-10-generic i686

[nirwana (weisbeek)]

Sounds like the Acid3-test has officially been released:
www.webstandards.org/press/releases/20080303/
www.webstandards.org/acid3/

[L. David Baron (dbaron)]

It looks like test 42 in the test is broken. The selector it uses is:
        var match = add("#div1 ~ div div + div > div");
but the content tree it constructs would match
        var match = add("#div1 ~ div + div div > div");

[L. David Baron (dbaron)]

Er, never mind.

[Darren VanBuren (onekopaka)]

we are falling behind webkit. they can do 90 of the tests while we only can do 66. we need to look at their code and see how things work there.

[Dao (dao)]

We need to ship Firefox 3 and Gecko 1.9.

[Matthew Tighe (tighem)]

I can confirm this

[ethana2 (ethana2)]

Thanks for the bugzilla links.

[Mackenzie Morgan (maco.m)]

(In reply to comment #20)
> we are falling behind webkit. they can do 90 of the tests while we only can do
> 66. we need to look at their code and see how things work there.
>

66? I got 60 completed on FF3b3 on Linux, and that's the highest I've seen. When I tried the first time, it was 57. One of my friends tried WebKit on his Mac, and it was 83, not 90.

[Zurtex (zurtex)]

(In reply to comment #22)
> 66? I got 60 completed on FF3b3 on Linux, and that's the highest I've seen.
> When I tried the first time, it was 57. One of my friends tried WebKit on his
> Mac, and it was 83, not 90.
>

Well on:

Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9b5pre) Gecko/2008030806 Minefield/3.0b5pre ID:2008030806

I get 69/100.

But could we keep this discussion to some forum ( e.g mozillazine ). It's not really worthy bug talk unless we expect to be getting some particular score and we're not.

[Asrail (asrail)]

69 on Linux, today's build.

[Zed260 (zed260)]

we need a rule for this acid test no posting number unless it has gone down or up or something like that

[Jonh-tomas (jonh-tomas)]

I think no one cares if this cames 1 month later or sooner... the important is that it cames free of bugs...

if there is a bug then it should be fixed before the final release.

And passing the Acid3 Test would be great, would bring confidence to users and would make a lot of publicity to Firefox (specially if it was the first browser to do so!)

[Matp75zilla (matp75zilla)]

Please move this kind of discussion to mozillazine forums as this bug is only a tracking bug and should be kept concise if possible : http://forums.mozillazine.org/viewtopic.php?t=634633&postdays=0&postorder=asc&postsperpage=15&start=0

[Mephiles (mephiles)]

I have a feeling that some features required to pass the test won't be added until Gecko 2 is out. Am I correct?

[Zed260 (zed260)]

yes you are josh the only way Firefox 3 could pass would be if we delayed Firefox 3 till early 2009 at the earliest

[Mephiles (mephiles)]

(In reply to comment #29)
> yes you are josh the only way Firefox 3 could pass would be if we delayed
> Firefox 3 till early 2009 at the earliest

Actually, Gecko 2 will be in Firefox 4.

[Crazy-daniel (crazy-daniel)]

Please don't spam this bug with discussions about its progress, progress that may happen or happend already and avoid discussing topics that are only slightly related to this bug at all, like the next iteration of Gecko/Firefox.

These topics are best discussed in the forums of MozillaZine.org Here's the Acid3 Topic: http://forums.mozillazine.org/viewtopic.php?t=634633

Vote or CC to this Bug if you want to follow its progress. Spamming the bug will only annoy the devs and those who already voted or CCd to follow its progres (like me). Thank you.

I apology for my own spam. Sorry.

[KeeperOS (feilakas-bugzilla)]

Using Firefox 3.0b4 under Windows XP PRO SP2 it shows inconsistent behavior.
More specifically I get 67/100 score 75% of the time and a 68/100 a 25%.

On those times that I get the 67 the extra test that fails is:
"Test 80 failed: kungFuDeathGrip is null"

I also noticed that the tests that have a 67 last 0.45 to 0.55 seconds while the ones that score 68/100 last at least 0.70 (in one instant I got a full 2.43!)

[Fred (eldmannen+launchpad)]

I can confirm this too.

68/100 on Mozilla Firefox 3.0 beta 4.
32 too few.

[Fred (eldmannen+launchpad)]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5pre) Gecko/2008032304 Minefield/3.0b5pre

March 23 build.
71/100 passed.
Still 29 too few.

[ethana2 (ethana2)]

Fred: do the nightlies display the right colors on the page yet?

[Mephiles (mephiles)]

(In reply to comment #32)
> Using Firefox 3.0b4 under Windows XP PRO SP2 it shows inconsistent behavior.
> More specifically I get 67/100 score 75% of the time and a 68/100 a 25%.
> On those times that I get the 67 the extra test that fails is:
> "Test 80 failed: kungFuDeathGrip is null"
> I also noticed that the tests that have a 67 last 0.45 to 0.55 seconds while
> the ones that score 68/100 last at least 0.70 (in one instant I got a full
> 2.43!)

This might actually be caused because of your cache. Reset it by pressing F5 and Ctrl at the same time. Tis happened to me on Minefield. It came up with a score of 70/100. After, I downloaded the latest build. I then went back on Acid3 and it was still 70, but a wikipedia article said it was 71, so I reset the cache and it was 71.

[KeeperOS (feilakas-bugzilla)]

(In reply to comment #33)
You know, this probably was it. I did it and now I get 78 systematically!

Great, thanks!

[Lukaswrites-bugzilla (lukaswrites-bugzilla)]

Firefox 4 beta 2 scores only 95/100 compared to firefox beta 1 97/100. What happened??

[Karl156 (karl156)]

The latest nightly is still working fine (97/100).

Failed 3 tests.
Test 26 passed, but took 60ms (less than 30fps)
Test 69 passed, but took 64 attempts (less than perfect).
Test 77 failed: expected '4776' but got '5560' - getComputedTextLength failed.
Test 78 failed: expected '90' but got '0' - getRotationOfChar(0) failed.
Test 79 failed: character position 1, which is between a normal character and the first character of a two-character glyph, is 72 but should be 10000.
Total elapsed time: 2.91s

Mozilla/5.0 (Windows; Windows NT 5.1; rv:2.0b3pre) Gecko/20100727 Minefield/4.0b3pre

[Sierkb (sierkb)]

HTML5, Modernized: Fourth IE9 Platform Preview Available for Developers
http://blogs.msdn.com/b/ie/archive/2010/08/04/html5-modernized-fourth-ie9-platform-preview-available-for-developers.aspx

Acid3 Score: 95/100

"As IE9 has implemented more of the standards that developers use and value, IE9’s Acid3 score has continued to rise. The remaining points involve two particular technologies (SVG Fonts and SMIL animation of SVG) that are in transition."

[Scott (scott001)]

Latest nightly status:

Failed 3 tests.
Test 26 passed, but took 44ms (less than 30fps)
Test 77 failed: expected '4776' but got '5550.625' - getComputedTextLength failed.
Test 78 failed: expected '90' but got '0' - getRotationOfChar(0) failed.
Test 79 failed: character position 1, which is between a normal character and the first character of a two-character glyph, is 72.21875 but should be 10000.
Total elapsed time: 0.65s

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7pre) Gecko/20100923 Firefox/4.0b7pre

[Scott (scott001)]

Current hourly only scores 94/100 and takes awhile to get there...

Failed 6 tests.
Test 26 passed, but took 44ms (less than 30fps)
Test 69 failed: timeout -- could be a networking issue
Test 75 failed: Permission denied for <http://acid3.acidtests.org> to get property HTMLDocument.documentElement from <moz-safe-about:neterror?e=fileNotFound&u=http%3A//acid3.acidtests.org/svg.xml&c=UTF-8&d=Firefox%20can%27t%20find%20the%20file%20at%20http%3A//acid3.acidtests.org/svg.xml.>.
Test 76 failed: Permission denied for <http://acid3.acidtests.org> to get property HTMLDocument.getElementById from <moz-safe-about:neterror?e=fileNotFound&u=http%3A//acid3.acidtests.org/svg.xml&c=UTF-8&d=Firefox%20can%27t%20find%20the%20file%20at%20http%3A//acid3.acidtests.org/svg.xml.>.
Test 77 failed: Permission denied for <http://acid3.acidtests.org> to get property HTMLDocument.documentElement from <moz-safe-about:neterror?e=fileNotFound&u=http%3A//acid3.acidtests.org/svg.xml&c=UTF-8&d=Firefox%20can%27t%20find%20the%20file%20at%20http%3A//acid3.acidtests.org/svg.xml.>.
Test 78 failed: Permission denied for <http://acid3.acidtests.org> to get property HTMLDocument.documentElement from <moz-safe-about:neterror?e=fileNotFound&u=http%3A//acid3.acidtests.org/svg.xml&c=UTF-8&d=Firefox%20can%27t%20find%20the%20file%20at%20http%3A//acid3.acidtests.org/svg.xml.>.
Test 79 failed: character position 1, which is between a normal character and the first character of a two-character glyph, is 72.21875 but should be 10000.
Total elapsed time: 6.37s

[L. David Baron (dbaron)]

(In reply to comment #118)
> Current hourly only scores 94/100 and takes awhile to get there...

Are you testing using a build from ftp.mozilla.org or a build that you made yourself?

[Zurtex (zurtex)]

(In reply to comment #118)
> Current hourly only scores 94/100 and takes awhile to get there...

Please run in a clean profile with no extensions(a few popular ones cause exactly what I see you getting) and give us your build id if it is really a regression.

[Scott (scott001)]

(In reply to comment #120)
> (In reply to comment #118)
> > Current hourly only scores 94/100 and takes awhile to get there...
>
> Please run in a clean profile with no extensions(a few popular ones cause
> exactly what I see you getting) and give us your build id if it is really a
> regression.

The only thing that changed since last time I ran it is my adblock subscriptions.. I disabled all extensions and still get 94/100.

[Lthere (helder-magalhaes)]

(In reply to comment #121)
> > Please run in a clean profile with no extensions(a few popular ones cause
> > exactly what I see you getting) and give us your build id if it is really a
> > regression.
>
> The only thing that changed since last time I ran it is my adblock
> subscriptions.. I disabled all extensions and still get 94/100.

Exactly, but you still have the extension there: I recall a somehow recent issue with Firebug which crashed Firefox even (when Firebug was) disabled. So please follow the comment 120 suggestion and create a brand new profile [1], don't install *any* extensions and then retry. ;-)

[1] http://kb.mozillazine.org/Profile_manager

[Raul-malea (raul-malea)]

Acid 3 test 97/100 FAILED (square - not blue!)

My Minefield:

about:buildconfig
Source

Built from http://hg.mozilla.org/mozilla-central/rev/2f456d0310fa
Build platform
target
i686-pc-mingw32
Build tools
Compiler Version Compiler flags
d;D:\mozilla-build\msys\mozilla-build\python25\python2.5.exe -O e;D:\mozilla-build\msys\builds\moz2_slave\mozilla-central-win32-nightly\build\build\cl.py cl 14.00.50727.762 -TC -nologo -W3 -Gy -Fdgenerated.pdb -DNDEBUG -DTRIMMED -Zi -Zi -UDEBUG -DNDEBUG -GL -wd4624 -wd4952 -O1
d;D:\mozilla-build\msys\mozilla-build\python25\python2.5.exe -O e;D:\mozilla-build\msys\builds\moz2_slave\mozilla-central-win32-nightly\build\build\cl.py cl 14.00.50727.762 -GR- -TP -nologo -Zc:wchar_t- -W3 -Gy -Fdgenerated.pdb -wd4800 -DNDEBUG -DTRIMMED -Zi -Zi -UDEBUG -DNDEBUG -GL -wd4624 -wd4952 -O1
Configure arguments

--enable-application=browser --enable-update-channel=nightly --enable-update-packaging --enable-jemalloc --enable-tests

[Frajjsen (frajjsen)]

Acid3 test 94/100 - something wrong? :)

[Bill-wg9s (bill-wg9s)]

(In reply to comment #124)
> Acid3 test 94/100 - something wrong? :)

Yes., This has been asked and answered numerous times in this bug already. Please read ALL the comments before commenting.

[Bill-wg9s (bill-wg9s)]

(In reply to comment #68)
> Add acid site to white list in Adblock plus :)

The actual domain to whitelist in adblock and noscript is acidtests.org.

[Cab26715 (cab26715)]

Current Minefield (1/11/11) reports a score of 97/100 with the following errors:

Failed 3 tests.
Test 26 passed, but took 64ms (less than 30fps)
Test 71 passed, but took 83ms (less than 30fps)
Test 77 failed: expected '4776' but got '5550.625' - getComputedTextLength failed.
Test 78 failed: expected '90' but got '0' - getRotationOfChar(0) failed.
Test 79 failed: character position 1, which is between a normal character and the first character of a two-character glyph, is 72.21875 but should be 10000.
Total elapsed time: 0.84s

[Cork (cork)]

(In reply to comment #127)
First see comment 111,

97/100 is the current status on acid3, and will most likely stay that way as there's a question for the need of svg font support (many of those failures comes from svg fonts see earlier comments from dbaron).

[Dpeelen (dpeelen)]

http://limi.net/articles/firefox-acid3 for more details on why it will stay on 97/100 (and why that’s a good thing)

ps. read #111 #126 and #128 BEFORE commenting.

[Nidaisfree (nidaisfree)]

https://bugzilla.mozilla.org/show_bug.cgi?id=119490#c63

A good implementation of SVG is needed. A good SVG implementation would mean passing the Acid3 test, but that's a byproduct, a collateral benefit. A good SVG implementation is needed per se.

This is a vicious circle: if browsers don't implement SVG fonts, developers won't use them. Developers won't use them because browsers don't implement them. The bug for SVG fonts was filed on 2002-01-11, 9 years ago, and its current status is ASSIGNED. 9 years and the bug is still there, and now the reasoning for not fixing it is that the feature is not used, it's probably going to have its specifications changed and because *now* WOFF is allegedly better. LOL. How could anyone have been using a feature that was not implemented? Of course a feature will likely be changed/deprecated after 9 years. And WOFF and SVG are not entirely interchangeable, i.e. It's nice to have WOFF, but SVG is still needed.

Does "Paste and Go" ring a bell? A bug was filed in 2002/3 requesting paste and go. It was left to rot into oblivion, dismissed by the developers, until Limi did a survey in Reddit last year and found out that people desperately wanted Paste and go (a really useful feature, by the way). Firefox 4 will finally implement Paste and Go. After 9 years. It would be nice if SVG fonts were also implemented. Gosh! You developers can be really stubborn!

[Shane B (helloimthegman)]

No browser fully supports SVG but would be a nice addition like in comment 130.

How does WebKit pass tests 77, 78 and 79? Those seem to be the tests still failing and it would be nice to take a look at how WebKit implements SVG fonts.

With Paste & Go it would be a great time saver and I use it all the time in Chromium.

I don't mind the devs being stubborn because you never know what they're up to!

[Laszlo Mocsar (lmocsi)]

(In reply to comment #123)
> Acid 3 test 97/100 FAILED (square - not blue!)

What is the status of the 2nd from right square being grey instead of blue? Is it also because of the svg-#@& ?

[Davemgarrett (davemgarrett)]

The squares represent each set of tests and are colored instead of grey when that set is fully passed. It's just another progress indicator. So yes, the 3/100 tests that aren't passed are the reason the 2nd to last square isn't blue.

Each comment here emails hundreds of people, so please, no more comments needed.

Just to keep the link in the last comment:
http://limi.net/articles/firefox-acid3

[Gandalf-aviary (gandalf-aviary)]

It seems that there are more issues with some of the Acid3 tests - http://annevankesteren.nl/2011/09/acid3-problem - and that they started collecting list of proposed changes to Acid3 - http://annevankesteren.nl/2011/09/changing-acid3 .
Should we add our remaining 3 items on that list?

[Webmaster-keryx (webmaster-keryx)]

Acid3 has now changed and Firefox gets 100/100, as does the latest IE.

https://plus.google.com/107429617152575897589/posts/JdHnqpuUER4

The details

Failed 0 tests.
Test 26 passed, but took 247ms (less than 30fps)
Test 69 passed, but took 11 attempts (less than perfect).
Test 71 passed, but took 53ms (less than 30fps)
Total elapsed time: 3.48s

Thus Firefox still fails that weird "smoothness criterion" that tech journalists are 100 % clueless about. And since all browsers now get 100 points we can assume that the test will no longer be used in articles and blog posts.

Proposing we mark this bug as FIXED

[Sprint69 (sprint69)]

I sure hope that it'll be marked as fixed, I've been trying to get out of the mailing list since eternity.. (I'm half-joking half-serious)

[Ms2ger (ms2ger)]

Fixed indeed, and lessons learned. Let us lay this test to rest now.

[Sierkb (sierkb)]

What about an update of
https://spreadsheets.google.com/pub?key=pNgBCwWdyRTT2JeiZn4B2Yw ?

Is this document still of any relevance (last updated: build 20100220)?

[Sierkb (sierkb)]

What about an update of
https://spreadsheets.google.com/pub?key=pNgBCwWdyRTT2JeiZn4B2Yw ?

Is that document still of any relevance (last updated: build 20100220)?

[Sierkb (sierkb)]

@admin:

Sorry for the triple-post and spamming the bug list (caused by a browser hang). Please ignore and delete the first two, leaving the most recent one of them.

[Davemgarrett (davemgarrett)]

(In reply to Sierk Bornemann from comment #141)
Comments are rarely deleted/hidden and not for the above sort of thing. Don't worry about it.

(In reply to Sierk Bornemann from comment #140)
> What about an update of
> https://spreadsheets.google.com/pub?key=pNgBCwWdyRTT2JeiZn4B2Yw ?
>
> Is that document still of any relevance (last updated: build 20100220)?

That appears to be out of date. Line #71 notes two pending bug numbers, both of which are now fixed. The page says up top it was last updated 20100220 (2010-02-20). I'd say it's obsolete.

(In reply to Lars Gunther from comment #135)
> Failed 0 tests.
> Test 26 passed, but took 247ms (less than 30fps)
> Test 69 passed, but took 11 attempts (less than perfect).
> Test 71 passed, but took 53ms (less than 30fps)
> Total elapsed time: 3.48s
>
> Thus Firefox still fails that weird "smoothness criterion" that tech
> journalists are 100 % clueless about.

Your time is way slower than what many others get. My runs are always way under a second and I usually only get two warning lines, sometimes one, and I suspect others may get none on faster systems. Attempting to measure stuff like this here was always going to be a problem because it's not going to have the same results for every system, not to mention the vagueness of saying "the animation has to be smooth". For the record, here's the sort of output I get for a new Firefox 6.0.2 profile on Linux using my laptop:

Failed 0 of 100 tests.
Test 26 passed, but took 70ms (less than 30fps)
Test 69 passed, but took 1 attempts (less than perfect).
Total elapsed time: 0.29s

Minefield gets similar results.

As far as I'm concerned, all of the stated criteria are fulfilled in the new Acid3 version. This is completely done now; I'll even mark this bug verified. I guess we're just waiting on Acid4 now. ;)

To everyone considering commenting here: All new comments email hundreds of people and this bug is done, so no more posting here, please.

[Philippe Cochy (packager-pecita)]

SVG fonts are an essential element of the architecture SVG. The reason is that XML structure allows to manipulate an SVG source consistently.
It seems to me that in Acid3test the test done on SVG fonts has been dishonestly removed: is that correct?

[Davemgarrett (davemgarrett)]

Again, this is not a discussion forum.
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

[E-yarl-l (e-yarl-l)]

Awesome, it has finally passed it.

[Vp2177+mozbugz (vp2177+mozbugz)]

Should be reopened, Fennec 14 final fails with score 99.

[Thomas Hotz (thotz-deactivatedaccount)]

I tested Firefox 16 and I got 100 points on Ubuntu 12.10.

[Thomas Hotz (thotz-deactivatedaccount)]

Tested on Ubuntu 13.04 and got 100 points, so marking as fixed here. Also the upstream bug is fixed. Thank you for reporting bugs to Ubuntu.

[Alex-fdm (alex-fdm)]

I believe I found a regression: test 72 is failing on Firefox 50 ("expected '10' but got '19' - prerequisite failed: style didn't affect image").

[Bill Gianopoulos (wgianopoulos)]

(In reply to Alexandre Folle de Menezes from comment #148)
> I believe I found a regression: test 72 is failing on Firefox 50 ("expected
> '10' but got '19' - prerequisite failed: style didn't affect image").

Are you testing with a new clean profile?, as the test conditions say you should?

[Ryanvm (ryanvm)]

I see 100/100 with Fx50 and a clean profile. On Nightly, the only failure I see is test 35, which is covered by bug 1311329. So yeah, I'd strongly suspect an addon interfering or something.

[Vp2177+mozbugz (vp2177+mozbugz)]

(In reply to Ryan VanderMeulen [:RyanVM] from comment #150)
> I see 100/100 with Fx50 and a clean profile. On Nightly, the only failure I
> see is test 35, which is covered by bug 1311329. So yeah, I'd strongly
> suspect an addon interfering or something.

I had the "Findbar Tweak" plugin/extension/add-on installed. Removing/uninstalling/disabling it makes Acid3 pass 100/100.

[Alex-fdm (alex-fdm)]

(In reply to Bill Gianopoulos [:WG9s] from comment #149)
> (In reply to Alexandre Folle de Menezes from comment #148)
> > I believe I found a regression: test 72 is failing on Firefox 50 ("expected
> > '10' but got '19' - prerequisite failed: style didn't affect image").
>
> Are you testing with a new clean profile?, as the test conditions say you
> should?

Indeed, I get 100/100 of FFox 50 when I disable all add-ons. Sorry for the noise.