237403 2022-03-02 18:54:53 -0800 Can't transfer an ImageBitmap through a MessageChannel 2025-12-09 00:27:57 -0800 1 1 1 Unclassified WebKit Canvas Safari Technology Preview Unspecified Unspecified RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 1 tristan.fraipont webkit-unassigned ahmad.saleem792 cdumez dino heycam karlcow kkinnunen sabouhallawa simon.fraser webkit-bug-importer oldest_to_newest 1847718 0 tristan.fraipont 2022-03-02 18:54:53 -0800 Transferring an ImageBitmap through the ports of a MessageChannel makes the `data` of the MessageEvent `null`. This doesn't happen when only cloning the ImageBitmap instead of transferring it. This also doesn't happen when transferring from a Worker's `postMessage` (this is being tested by WPT), nor when transferred from an WindowProxy, i.e this only concerns MessageChannel. You can see a minimal repro at https://jsfiddle.net/1kzxvad9/ 1849941 1 webkit-bug-importer 2022-03-09 18:55:15 -0800 <rdar://problem/90072516> 2164351 2 ahmad.saleem792 2025-12-09 00:02:57 -0800 *** Safari 26.2 Beta *** "clone", [object ImageBitmap] { close: function close() { [native code] }, height: 20, width: 20 } "transfer", [object ImageBitmap] { close: function close() { [native code] }, height: 20, width: 20 } *** Chrome Canary 144 *** "clone", [object ImageBitmap] { close: function close() { [native code] }, height: 20, width: 20 } "transfer", [object ImageBitmap] { close: function close() { [native code] }, height: 20, width: 20 } *** Firefox Nightly 148 *** clone", [object ImageBitmap] { close: function close() { [native code] }, height: 20, width: 20 } "transfer", [object ImageBitmap] { close: function close() { [native code] }, height: 20, width: 20 } _________ All browsers now match, It might have been fixed while it was reported. @Karl - anything I missed, or we can mark as `Config Changed`? 2164354 3 tristan.fraipont 2025-12-09 00:26:51 -0800 It probably has been fixed, indeed. 2164355 4 ahmad.saleem792 2025-12-09 00:27:57 -0800 (In reply to Kaiido from comment #3) > It probably has been fixed, indeed. Thanks for confirming.