Closed Bug 1348272 Opened 8 years ago Closed 2 years ago

Mark nsIOutputStream as builtinclass

Categories

(Core :: XPCOM, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
106 Branch
Tracking Status
firefox106 --- fixed

People

(Reporter: hsivonen, Assigned: nika)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

We should mark nsIOutputStream as builtinclass in order to be able to stop worrying about bug 170416.
Priority: -- → P3

FWIW, it looks like test_async_response_sending.js is the only one of the three tests in comment 1 that still uses nsIOutputStream in JS, at least at a glance. I don't know if there are others.

We should look into whether we can get rid of that caller, as we definitely don't make sure to null-terminate all calls to nsIOutputStream::write nowadays, and it'd be nice to make sure that we can't add new JS implementations.

Assignee: nobody → nika
Status: NEW → ASSIGNED
Pushed by nlayzell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/10ea141649b6 Mark nsIInputStream and nsIOutputStream as builtinclass, r=xpcom-reviewers,necko-reviewers,barret,valentin

Backed out changeset 10ea141649b6 (Bug 1348272) for causing mochitest failures on test_domparsing.xhtml.
Backout link
Push with failures <--> c2
Failure Log

Flags: needinfo?(nika)
Pushed by nlayzell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1d172cf70c68 Mark nsIInputStream and nsIOutputStream as builtinclass, r=xpcom-reviewers,necko-reviewers,barret,valentin
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
Regressions: 1790177
Flags: needinfo?(nika)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: