Closed Bug 1035300 Opened 11 years ago Closed 11 years ago

css coverage report shows incorrect data when run with oneshot

Categories

(DevTools :: Style Editor, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 33

People

(Reporter: jwalker, Assigned: jwalker, Mentored)

References

Details

Attachments

(1 file)

No description provided.
The "csscoverage oneshot" command in /toolkit/devtools/gcli/commands/csscoverage.js isn't going to be exposes in the main UI, and it's not the end of the world if we leave it hidden. The CSSUsageActor (/toolkit/devtools/server/actors/csscoverage.js) should mark itself (this._isOneShot=true or similar) if its data was created using "oneshot" and if createPageReport is called in oneshot mode, we should throw. Finally the "csscoverage report" command should make sure it displays a suitable error message.
Mentor: jwalker
Whiteboard: [good first bug][lang=js]
Assignee: nobody → jwalker
Status: NEW → ASSIGNED
Attachment #8454456 - Flags: review?(fayearthur)
Attachment #8454456 - Flags: review?(fayearthur) → review+
Keywords: checkin-needed
Whiteboard: [good first bug][lang=js]
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 33
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: