Closed Bug 1356458 Opened 7 years ago Closed 6 years ago

Drive Stylo static analysis hazard threshold to zero

Categories

(Core :: CSS Parsing and Computation, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: bholley, Assigned: sfink)

References

Details

(Whiteboard: [Stylo])

Steve landed the analysis in bug 1294915 (\o/) but there are still 7 hazards, and actually 9 as of a few minutes ago. We have a threshold value to prevent us from adding more, but we should drive that number to zero. We have some dependent bugs about this already, which I've assigned to Manish for easy fixes or triaging.
Depends on: 1356610
Depends on: 1356266
Depends on: 1356267
Depends on: 1356275
Depends on: 1356276
Depends on: 1356305
We should try to fix all of Stylo's static analysis hazards before we enable Stylo by default on Nightly.
Blocks: stylo-nightly
No longer blocks: stylo
I think I've fixed all of the actual bugs in the code (and updated the whitelist as much as I can.)

The remaining ones seem to be cases  where the current analysis is inadequate. Steve, can you take it from here?
Assignee: manishearth → sphink
Flags: needinfo?(sphink)
Priority: P1 → --
This is work that needs to happen on the analysis, which Steve committed to doing this month. Switching categories.
Summary: stylo: Drive static analysis hazard threshold to zero → drive static analysis hazard threshold to zero
Whiteboard: [Stylo]
Depends on: 1368922
Depends on: 1400435
Depends on: 1400438
Depends on: 1400442
Depends on: 1401775
The threshold is now zero.
Flags: needinfo?(sphink)
(In reply to Steve Fink [:sfink] [:s:] from comment #4)
> The threshold is now zero.

Steve, can we resolve this Stylo hazard bug as fixed? Do you know of any remaining work or cleanup?
Flags: needinfo?(sphink)
Summary: drive static analysis hazard threshold to zero → Drive Stylo static analysis hazard threshold to zero
Yeah, this does seem to be fixed.

Let's see, I had some ideas for how to make things a little nicer -- eg, having an easy way to mark safe outparams in the source. But that sort of thing seems like it should be a separate bug anyway.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(sphink)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.