Launchpad has imported 35 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1311329.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2016-10-19T12:40:02+00:00 Bill Gianopoulos wrote:
Under both Aurora and nightly ACID3 test 35 is failing with this error:
Test 35 failed: expected '0' but got '1' - root element, with no parent
node, claims to be a :first-child
Current relase and Beta are NOT affected.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/0
On 2016-10-19T13:02:07+00:00 Bill Gianopoulos wrote:
This fails under WIndows as well.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/1
On 2016-10-19T14:41:19+00:00 Mats-l wrote:
Is this an intentional change from bug 1300374?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/2
On 2016-10-19T14:46:30+00:00 Bill Gianopoulos wrote:
(In reply to Mats Palmgren (:mats) from comment #2)
> Is this an intentional change from bug 1300374?
If this is an intentional change, and the reasons for the change are
legitimate, then we should ask to have the test changed. That said,
Google Chrome still gets 100% on this test. I will try backing out that
change to see how it impacts the test results.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/3
On 2016-10-19T15:14:15+00:00 Bill Gianopoulos wrote:
I have verified that restoring this code:
if (!parent) {
return false;
}
from edgeChildMatches
which was removed by the patch for bug 1300374 does restore the 100%
result in the Acid3 test.
I also wonder why this was not known , if it was not, because I thought
we included the Acid3 test in the our test suite.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/4
On 2016-10-19T15:20:58+00:00 B-emilio wrote:
Yes, this is intentional, since the spec changed. If it breaks stuff we
can of course restore the old behavior (though I won't say Acid3 is
representative of actual content, and this is the first report related
to that bug AFAIK).
I think we should get the test changed, but I don't know how feasible is
it.
Also, no, I don't think we include Acid3 in our test suite (otherwise
that patch would've never landed).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/5
On 2016-10-19T15:51:11+00:00 Ms2ger wrote:
Fixing Acid3 has historically not been an issue. I asked Hixie
.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/6
On 2016-10-21T02:29:02+00:00 Bmo-7 wrote:
(In reply to Emilio Cobos Álvarez [:emilio] from comment #5)
> I think we should get the test changed, but I don't know how feasible is it.
Will this change cause any webcompat issue here between Blink and us ?
Following the spec is correct but still concerned about breakage of any
websites due to compatibility issues.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/7
On 2016-10-21T08:52:43+00:00 B-emilio wrote:
Hi Astley,
As I said before, I don't think Acid3 is representative of actual
content, so I don't think sites rely on this.
That being said, yes, it's a difference, but this is the first report
related to that change in two months, and it's in a fairly artificial
test.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/8
On 2016-10-24T13:35:11+00:00 Bmo-7 wrote:
So could we change to Tech Evangelism team to help the fix on ACID3 test
cases?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/9
On 2016-10-24T16:10:48+00:00 Ms2ger wrote:
No need. I'll try to poke again this week.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1690006/comments/10
On 2016-10-24T16:18:05+00:00 Bill Gianopoulos wrote:
Problem
