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

Issue 770221 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 639631
Owner:
Last visit 28 days ago
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Default style rule is not correct when object contains dots in its id

Reported by petr.ple...@booking.com, Sep 29 2017

Issue description

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

Steps to reproduce the problem:
1. Create any html element containing . in the id 
like
fin.ar.customerinvoicelist.InvoiceList--createPromiseBtn
2. Inspect element
3. Go to Styles tab and try to create new style with + button.

What is the expected behavior?
As this element contains dots in the id they must be delimited with / symbol in the selector.
I expect to see :
#fin\.ar\.customerinvoicelist\.InvoiceList--createPromiseBtn

What went wrong?
Instead I see:
#fin.ar.customerinvoicelist.InvoiceList--createPromiseBtn

which is ignored by the browser.

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

It looks very confusing when you create a style for the element and it's just ignored immediately.
 
chrome_2017-09-29_17-57-16.png
94.4 KB View Download

Comment 2 by woxxom@gmail.com, Sep 29 2017

0. open the attached test.html
1. Right-click the text
2. Inspect
3. Press + in Styles sub-panel toolbar

EXPECTED1 (best):  pre#a\.b\.c
EXPECTED2 (worse): pre#a\2e b\2e c
OBSERVED:          pre#a.b.c

Bisect info: 257481 (good) - 257486 (bad)
https://chromium.googlesource.com/chromium/src/+log/48330e9c..7448ef66?pretty=fuller
Suspecting r257486 "Blink roll 169292:169364"
Landed in 35.0.1897.0

This bisect info is probably not really useful because:
1) Chrome never displayed the best possible result: pre#a\.b\.c
2) Chrome result before r257486 was too verbose:    pre#a\2e b\2e c
3) the code was rewritten since then.

The bug was never fixed and still present in Canary 63.
test.html
209 bytes View Download
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Mergedinto: 639631
Status: Duplicate (was: Assigned)

Sign in to add a comment