New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 718708 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

acid3 test #23 failed

Reported by extrom...@gmail.com, May 5 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3088.3 Safari/537.36

Example URL:
http://acid3.acidtests.org/

Steps to reproduce the problem:
1. Visit acid3.acidtests.org
2. Only get 97 of 100 score

What is the expected behavior?
1. Visit acid3.acidtests.org
2. Get 99 of 100 score (Due to previous chromium  bug #689878 )

What went wrong?
From the log of acid3 test:
Test 23 failed: expected '14' but got '5' - wrong exception for createElementNS('null', ':div')

Does it occur on multiple sites: N/A

Is it a problem with a plugin? No 

Did this work before? Yes 60.0.3080.5

Does this work in other browsers? Yes

Chrome version: 60.0.3088.3  Channel: dev
OS Version: 
Flash Version: Shockwave Flash 25.0 r0
 

Comment 1 by ajha@chromium.org, May 5 2017

Cc: tkent@chromium.org ajha@chromium.org foolip@chromium.org f...@opera.com
Labels: -Pri-2 -Type-Compat hasbisect-per-revision ReleaseBlock-Stable M-60 OS-Mac OS-Windows Pri-1 Type-Bug-Regression
Owner: shanmug...@samsung.com
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on the latest M-60(60.0.3090.0) on Windows-10,Mac OS 10.12.3 and Linux Ubuntu 14.04.

Regressed in M-60.

Last good build: 60.0.3083.0
First bad build: 60.0.3084.0

Changelog:
=========
https://chromium.googlesource.com/chromium/src/+log/a8c329d4466035b680575a794744e469641e7b9b..423b422b6ce147aa3bb4858ab498802751c52c9b

shanmuga.m@: Could you please take a look at this.

Thank you!

Comment 2 by ajha@chromium.org, May 5 2017

 Issue 718709  has been merged into this issue.

Comment 3 by f...@opera.com, May 5 2017

This came up and was discussed while making the change to the spec: https://github.com/whatwg/dom/issues/319#issuecomment-296345763
The consensus seems to be to ignore this failure. (WebKit and Gecko have both adapted the same behavior, see references in the spec issue discussion.)

Comment 4 by tkent@chromium.org, May 7 2017

Components: Blink>DOM
Status: WontFix (was: Assigned)
IMO acid3 is obsolete, and we should not refer to it any longer.

Sign in to add a comment