Closed Bug 863770 Opened 11 years ago Closed 11 years ago

nsBinaryInputStream::ReadAsArrayBuffer needs to take an ArrayBuffer input

Categories

(Core :: XPCOM, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla23
blocking-b2g tef+
Tracking Status
firefox23 --- fixed
b2g18 --- fixed
b2g18-v1.0.0 --- wontfix
b2g18-v1.0.1 --- fixed

People

(Reporter: jdm, Assigned: jdm)

References

Details

(Whiteboard: [fixed-in-birch])

Attachments

(1 file)

Sometimes it matters in which compartment the ArrayBuffer is created, so we should have consumers pass in one for the method to use instead of creating one itself.
This is required to make the email app work after bug 831107.
blocking-b2g: --- → tef?
Blocks a blocker.
Blocks: 863807
blocking-b2g: tef? → tef+
It seems like Josh is on this.
Assignee: nobody → josh
Whiteboard: [status: patches awaiting review]
Comment on attachment 739653 [details] [diff] [review]
Pass in an ArrayBuffer object for nsBinaryInputStream::ReadAsArrayBuffer to use, for cases when the compartment in which it resides matters.

r+, but can you add an explicit comment to watch out if passing in SomeView.buffer, because the view might not start at byte 0 of the buffer.
Attachment #739653 - Flags: review?(vladimir) → review+
https://hg.mozilla.org/mozilla-central/rev/a991d0f4469b
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
Blocks: 865335
Depends on: 886393
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: