Open
Bug 1348485
Opened 7 years ago
Updated 2 months ago
Deprecate nsIScriptableInputStream and nsIStringInputStream
Categories
(Core :: XPCOM, enhancement, P3)
Core
XPCOM
Tracking
()
NEW
| Performance Impact | none |
People
(Reporter: kmag, Unassigned)
References
(Blocks 1 open bug)
Details
These are two sides of the same coin. JS callers should use nsIBinaryInputStream and nsIArrayBufferInputStream to read and write ArrayBuffers respectively. nsIStringInputStream is still useful from native code, so it should be made non-scriptable rather than removed.
Blocks: post-57-api-changes
No longer depends on: post-57-api-changes
Still some uses in c-c, https://dxr.mozilla.org/comm-central/search?q=nsIStringInputStream&redirect=false
|
||
Updated•7 years ago
|
Whiteboard: [qf]
|
|
||
Updated•7 years ago
|
Whiteboard: [qf] → [qf-]
|
||
Updated•7 years ago
|
Priority: -- → P3
|
||
Updated•2 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-]
|
||
Updated•2 years ago
|
Severity: normal → S3
| Comment hidden (spam) |
You need to log in
before you can comment on or make changes to this bug.
Description
•