CSS coverage should check each selector in a group separately
Reported by
redge.on...@gmail.com,
Jul 2
|
||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
Steps to reproduce the problem:
Given the following sample page:
<html>
<head>
<style>
h1, .not-used { font-weight: normal; }
</style>
</head>
<body>
<h1>Example</h1>
</body>
</html>
What is the expected behavior?
The coverage tool should report that one of the selectors in the style rule is not used.
What went wrong?
The coverage tool will report the entire style rule as used.
Did this work before? No
Chrome version: 67.0.3396.99 Channel: stable
OS Version: Ubuntu 16.04.4 LTS
Flash Version:
,
Jul 6
Thanks for filing the issue... Unble to reproduce the issue on reported chrome version 67.0.3396.99 using Using Ubuntu 17.10. Steps: --------- 1. Launched reported chrome 2. Created html file by using html code in the commment #0 3. Dropped the html in to new tab 4. Opened Dev tools and inspected the ""Example"" As we are able to see the style rule is not used.Attaching screenshot for reference. @Reporter: @Reporter:Request you to check and confirm if anything is missed from our end in reproducing the issue and any further information will help in better triaging. If possible can you provide screenshot for expected behavior/ wrong behavior. Thanks..!
,
Jul 9
Ah, you misunderstand: I was talking about the code coverage tool. Please see attached screenshot: notice the green indicator on the fourth line. This is misleading. The fourth line is marked as used, even though it is only partially used.
,
Jul 9
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
,
Jul 9
I understand why you want this, but unfortunately, that's how our style engine works. This is a good idea for a feature request, but as the engineer time is exceedingly high, you'll have to pursue a workaround.
,
Jul 9
Yeah, I kind of expected that. I'll see if I can figure out some way of having the CSS built without multiple selectors in it. Thanks for your time! |
||||
►
Sign in to add a comment |
||||
Comment 1 by viswa.karala@chromium.org
, Jul 2