Bug 64629
Summary: | Umbrella bug: implement transferable typed array support. | ||
---|---|---|---|
Product: | WebKit | Reporter: | Luke Zarko <lukezarko+bugzilla> |
Component: | New Bugs | Assignee: | Dmitry Lomov <dslomov> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | annevk, cmarcelo, dimich, dslomov, fpizlo, kbr, levin, yutak |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Bug Depends on: | 63481, 65209, 66578, 66829 | ||
Bug Blocks: |
Luke Zarko
Typed arrays should become Transferable (ref. http://www.whatwg.org/specs/web-apps/current-work/complete/common-dom-interfaces.html#transferable-objects)-- that is, it should be possible to pass a typed array using postMessage such that control of the data is sent but the array's data is not copied.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Kenneth Russell
After more discussion on public-webapps, only the ArrayBuffer type will be Transferable -- the typed array views will not be.
Note, though, that transfer of an ArrayBuffer necessitates side-effects on the views that refer to it, in order to cause their lengths to go to zero. However, this is essentially an implementation detail.
I suspect that this bug should be closed, and the work done under Issue 66578.
David Levin
(In reply to comment #1)
> this bug should be closed, and the work done under Issue 66578.
This is just the master bug for the feature. I suspect there will be no patches for it directly, and it will be resolved after all bugs that it depends on have been resolved.
David Levin
(In reply to comment #2)
> (In reply to comment #1)
> > this bug should be closed, and the work done under Issue 66578.
>
> This is just the master bug for the feature. I suspect there will be no patches for it directly, and it will be resolved after all bugs that it depends on have been resolved.
fwiw like this: https://bugs.webkit.org/show_bug.cgi?id=68822
Kenneth Russell
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > this bug should be closed, and the work done under Issue 66578.
> >
> > This is just the master bug for the feature. I suspect there will be no patches for it directly, and it will be resolved after all bugs that it depends on have been resolved.
>
> fwiw like this: https://bugs.webkit.org/show_bug.cgi?id=68822
I see. I wasn't sure which was the umbrella bug.
Anne van Kesteren
Done.