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

Issue 849634 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 609848
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

getComputedStyle(testDiv, null).getPropertyValue("content") returning 'normal' with latest chrome 67

Reported by satyanar...@gmail.com, Jun 5 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.62 Safari/537.36

Steps to reproduce the problem:
1. Run the attached code in console
2. 
3. 

What is the expected behavior?
It should return/print empty string

What went wrong?
It's returning/printing 'normal' which isn't expected

Did this work before? Yes 66

Does this work in other browsers? N/A

Chrome version: 67.0.3396.62  Channel: stable
OS Version: 8.1
Flash Version: 

Similar to Chrome 51 issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=609848
 
Chrome67_Issue.txt
475 bytes View Download
below is the code snippet to check the issue
----------------------
function testElementStyle(tag, id, property){
 		// test an element's style
		var docElement = document.documentElement;
		var testDiv = docElement.insertBefore(document.createElement(tag), docElement.firstChild);
		testDiv.id = id;
		var styleValue = (testDiv.currentStyle || getComputedStyle(testDiv, null))[property];
		docElement.removeChild(testDiv);
 		return styleValue;
 	} 
	
var parser = testElementStyle('x-parse', null, 'content');
console.log(parser);
------------------------

Comment 2 by woxxom@gmail.com, Jun 5 2018

The new behavior was introduced in 11fb2ae26b6e84211adf8270eb4f0cf42b945fe8 (67.0.3365.0) and it correctly implements the specification. 

  Computed value on elements is by default 'normal'
  and on :before and :after computes to 'none'
  Spec: https://www.w3.org/TR/CSS2/generate.html#content
Components: Blink>CSS
Labels: Needs-Bisect Needs-Triage-M67
Cc: ramy...@samsung.com
Labels: -Needs-Bisect Triaged-ET RegressedIn-67 M-67 Target-67 FoundIn-67 Target-68 Target-69 FoundIn-69 FoundIn-68 OS-Linux OS-Mac
Able to reproduce the issue on Windows 10, mac 10.13.3 and Ubuntu 17.10 using chrome reported version #67.0.3396.62 and latest canary #69.0.3451.0.

This seems to be an intended behaviour as per comment #2 that was introduced in 11fb2ae26b6e84211adf8270eb4f0cf42b945fe8 (67.0.3365.0).
ccing ramya.v@ for further inputs on this issue.

Thanks...!!


Thanks all for the quick response.

Might be third party libraries might have designed based on the browser response for the earlier versions (seems to be other browsers didn't implement this way). I will also check if libraries have any update.
Cc: phanindra.mandapaka@chromium.org pbomm...@chromium.org
 Issue 849984  has been merged into this issue.
Labels: -Needs-Triage-M67
Mergedinto: 609848
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment