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

Issue 850744 link

Starred by 4 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

getComputedStyle() doesn't accurately return custom CSS on ::placeholder pseudo-element

Reported by impressi...@gmail.com, Jun 7 2018

Issue description

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

Steps to reproduce the problem:
1. Apply custom CSS to the ::placeholder pseudo-element on an input
2. Use getComputedStyle() to retrieve the custom CSS

What is the expected behavior?
The return value should reflect the custom CSS

What went wrong?
The custom CSS is not reflected in the return value

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 66.0.3359.181  Channel: n/a
OS Version: 10.0
Flash Version: 

The values returned are the initial values for the pseudo-element, so the method is returning CSS, just not the correct CSS.

Also, this works fine using other pseudo-elements like :before, :after, and ::first-line.

This works in latest Firefox, but not in latest stable Chrome. Did not test in Canary or other pre-stable version.
 
bug-rtc.html
809 bytes View Download
Labels: Needs-Triage-M66
Cc: krajshree@chromium.org
Components: Blink>CSS
Labels: Triaged-ET Needs-Feedback
Tested the issue on Win-10 using chrome reported version #66.0.3359.181, latest stable #67.0.3396.79 and latest canary #69.0.3453.0.

Attached a screen shots for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened the attached file "bug-rtc.html"
2. Observed rgb(0,0,0) 400 in dev tools console.

reporter@ - Could you please check the attached screen shots and please let us know if anything missed from our end.

Thanks...!!
850744@M67stable.PNG
61.4 KB View Download
850744@M60.PNG
58.3 KB View Download
Yep, that looks like the same result I got (i.e. the wrong output). Thanks.
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 8 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: phanindra.mandapaka@chromium.org
Labels: -Type-Bug -Pri-2 RegressedIn-62 M-69 Target-69 Target-67 FoundIn-67 Target-68 FoundIn-68 FoundIn-69 hasbisect OS-Linux OS-Mac Pri-1 Type-Bug-Regression
Owner: drott@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on the reported chrome 66.0.3359.181,latest canary 69.0.3453.0 also on latest stable 67.0.3396.79 using Windows 10,Mac 10.13.3, Ubuntu 17.10. Below is the bisect information for same.

Bisect Info:
================
Good build: 62.0.3166.0
Bad build: 62.0.3167.0

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/c2e00edd1a2375452007ce81ee593c7225a60936..ba05045c920078d04b7135144dd14c649bc73727

Suspect: https://chromium-review.googlesource.com/c/chromium/src/+/574167

Reviewed-on: https://chromium-review.googlesource.com/574167

drott:Please confirm the issue and help in re-assigning if it is not related to your change.

Thanks!
The original report is not about 'normal' vs '400' which is drott's change. The attached test-case is setting font-weight 'bold' on the ::placeholder element but gets normal/400 from getComputedStyle.

The reported issue is probably a non-regression and the "regression" shown in the screen shots is an intentional fix from drott to align with the newest spec.

Labels: -Pri-1 -hasbisect -Type-Bug-Regression -M-69 -Triaged-ET -RegressedIn-62 -FoundIn-67 -FoundIn-68 -FoundIn-69 -Target-67 -Target-68 -Target-69 -Needs-Triage-M66 Pri-3 Type-Bug

Comment 8 by cnardi@chromium.org, Jun 13 2018

Owner: ----
Status: Available (was: Assigned)
Per #6.
Cc: vamshi.kommuri@chromium.org
 Issue 884537  has been merged into this issue.

Sign in to add a comment