Contact emails
xida...@chromium.org, ju...@chromium.org
Spec
https://html.spec.whatwg.org/#images
Summary
The ImageBitmap.close() method disposes of all graphical resources associated with an ImageBitmap.
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Demo link
No demos. But the developers can turn on experimental canvas features flag in browser to try this feature.
This MDN page: https://developer.mozilla.org/en-US/docs/Web/API/ImageBitmap/close provides a typical usage of this method.
Debuggability
This feature does not require special debugging support on its own.
Interoperability and Compatibility Risk
Interoperability risk is low. Firefox has release this feature in version 46 (https://developer.mozilla.org/en-US/Firefox/Releases/46). Other browsers have no public signals yet. Compatibility risk is low, as this does not remove or change existing features.
OWP launch tracking bug
Entry on the feature dashboard
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
close
()Releases imageBitmap's underlying bitmap data.
Hi Chris,The spec says:
- imageBitmap .
close
()Releases imageBitmap's underlying bitmap data.
In Blink, after calling ImageBitmap.close(), ImageBitmap's width and height become 0. I hope that answers your question.
On Thu, Apr 21, 2016 at 5:33 PM, Chris Harrelson <chri...@chromium.org> wrote:
> What will Blink's actual behavior be if you try to use an ImageBitmap after
> close()? It seems undefined according to spec.
Where is it undefined?
--
https://annevankesteren.nl/
On Thu, Apr 21, 2016 at 8:45 AM Xida Chen <xida...@chromium.org> wrote:Hi Chris,The spec says:
- imageBitmap .
close
()Releases imageBitmap's underlying bitmap data.
In Blink, after calling ImageBitmap.close(), ImageBitmap's width and height become 0. I hope that answers your question.Yes, that was my question. Then it's equivalent to a 0x0 image? Sounds reasonable. LGTM2.