Open
Bug 1347873
Opened 8 years ago
Updated 4 months ago
nsIStreamLoader should support receiving the data as an ArrayBuffer
Categories
(Core :: Networking, enhancement, P3)
Core
Networking
Tracking
()
NEW
| Performance Impact | none |
People
(Reporter: hsivonen, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: perf, Whiteboard: [necko-backlog])
The Web Platform represents binary data as ArrayBuffers instead of low 8 bits of each 16 bits of a JS string.
To allow chrome code to migrate to WebIDL APIs that expect ArrayBuffers, nsIStreamLoader should have an option to receive the data as an ArrayBuffer.
|
||
Updated•8 years ago
|
Whiteboard: [necko-backlog]
|
||
Updated•8 years ago
|
Whiteboard: [necko-backlog] → [necko-backlog][qf]
|
|
||
Updated•8 years ago
|
Whiteboard: [necko-backlog][qf] → [necko-backlog][qf-]
|
||
Comment 1•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
||
Updated•3 years ago
|
Performance Impact: --- → -
Whiteboard: [necko-backlog][qf-] → [necko-backlog]
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•