Terjemahan ini belum lengkap. Sila bantu terjemahkan artikel ini daripada Bahasa Inggeris.
The Transferable interface represents an object that can be transfered between different execution contexts, like the main thread and Web workers.
This is an abstract interface and there isn't any object of this type. It also doesn't define any method or property: it is merely a tag indicating objects that can be used in specific conditions, like to be transfered to a Worker using the Worker.postMessage() method.
The ArrayBuffer and MessagePort implement it.
Properties
The Transferable interface doesn't implement nor inherit specific properties.
Methods
The Transferable interface doesn't implement nor inherit specific properties.
Specifications
| Specification | Status | Comment |
|---|---|---|
| WHATWG HTML Living Standard The definition of 'Transferable' in that specification. |
Living Standard | No change from HTML5, though the new CanvasProxy does implement Transferable. |
| HTML5 The definition of 'Transferable' in that specification. |
Recommendation | Initial definition. |
Browser compatibility
| Feature | Chrome | Firefox (Gecko) | Internet Explorer | Opera | Safari (WebKit) |
|---|---|---|---|---|---|
| Basic support | (Yes) | 4.0 (2.0) | 10.0 [1] | (Yes) | (Yes) |
MessagePort |
? | Not supported | ? | ? | ? |
| Feature | Android | Firefox Mobile (Gecko) | IE Phone | Opera Mobile | Safari Mobile |
|---|---|---|---|---|---|
| Basic support | (Yes) | 4.0 (2.0) | 10.0 [1] | (Yes) | (Yes) |
MessagePort |
? | Not supported | ? | ? | ? |
[1] Internet Explorer 10 only accepts a single Transferable object as parameter, but not an array.
See also
- Interfaces implementing it:
ArrayBuffer,MessagePort.