Open Bug 1031963 Opened 11 years ago Updated 3 years ago

csscoverage report shows incorrect diagram data

Categories

(DevTools :: Style Editor, defect, P3)

33 Branch
defect

Tracking

(Not tracked)

People

(Reporter: sime.vidas, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release) Build ID: 20140605174243 Steps to reproduce: Test A: 1. Open this page in Firefox Nightly: http://direct.webplatformdaily.org/csscoverage.html 2. Open the CLI (Ctrl + F2) and run "csscoverage oneshot", then "csscoverage report" Test B: 1. On the same page, close DevTools/CLI and reload the page, then open the DevTools on the Debugger panel. 2. Reload the page again. The page rendering will be paused at the debugger; <script> 3. Run "csscoverage oneshot", then resume the break point, then run "csscoverage report" Actual results: Test A: The report shows: Used = 5, Unused = 5 Test B: The report shows: Used = 5, Unused = 3 Expected results: Test A: The report should show: Used = 5, Unused = 0 Test B: The report should show: Used = 3, Unused = 2
This is reproducible on Nightly on OS X as well. Joe? :-)
Status: UNCONFIRMED → NEW
Component: Untriaged → Developer Tools: Style Editor
Ever confirmed: true
Flags: needinfo?(jwalker)
OS: Windows 8.1 → All
Hardware: x86_64 → All
Version: 30 Branch → 33 Branch
Assignee: nobody → jwalker
Flags: needinfo?(jwalker)
TL;DR We should re-visit this once bug 1035300 is fixed. There are probably 2 parts to this type of problem. Bug 1035300 is for oneshot just not being good enough for reports. The second is what happens when the debugger allows page load to happen at unexpected times. I think we're likely to say that results are invalid if you do that, or that coverage stops when a breakpoint is hit.
Assignee: jwalker → nobody
Inspector bug triage (filter on CLIMBING SHOES).
Priority: -- → P3
Product: Firefox → DevTools
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.