Closed Bug 1013886 (enable-csscoverage) Opened 10 years ago Closed 4 years ago

[meta] CSS Coverage should be preffed on by default

Categories

(DevTools :: Style Editor, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jwalker, Unassigned)

References

(Depends on 2 open bugs)

Details

(Keywords: meta, Whiteboard: [status:landedoff])

By which I mean, the commands should have "hidden:true" removed.
There is no actual pref.
Depends on: 1013887
Depends on: 975522
Depends on: 1013896
Depends on: 1013897
Depends on: 1013909
Depends on: 1014223
Depends on: 1016285
Depends on: 1016288
Depends on: 1016330
Depends on: 1022587
Depends on: 1023943
Depends on: 1025044
Depends on: 1034062
Depends on: 1034181
Depends on: 1013356
Depends on: 1035300, 1035296
Depends on: 1023891
Whiteboard: [status:landedoff]
How can this feature be used at the moment? And is it still too unstable to enable it by default?

Sebastian
Flags: needinfo?(jwalker)
It can be used via hidden GCLI commands. 'csscoverage [start|stop|restart]'
It doesn't always get correct results, so it's not ready to be turned on.
Flags: needinfo?(jwalker)
Inspector bug triage (filter on CLIMBING SHOES).
Severity: normal → enhancement
Keywords: meta
Priority: -- → P3
Alias: enable-csscoverage
Depends on: 1163290
Product: Firefox → DevTools

CSS coverage went away with the removal of GCLI, right? So I guess this bug should be closed as INVALID.
(CSS coverage might still be integrated into the Style Editor at some point, though, which is covered in bug 1016288.)

Sebastian

Flags: needinfo?(gl)
Flags: needinfo?(gl)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.