- From: <bugzilla@jessica.w3.org>
- Date: Wed, 11 Jun 2014 16:01:37 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26060
Aaron Colwell <acolwell@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |acolwell@google.com
--- Comment #1 from Aaron Colwell <acolwell@google.com> ---
I'm not sure this will provide the benefits you are hoping for. Append, remove,
and duration change operations explicitly change JavaScript visible
HTMLMediaElement state. Even if the calls on the MediaSource object were done
in the worker, you'd still have to synchronize with the main thread to make
sure the HTMLMediaElement properly reflects the current state of MediaSource
object.
It isn't clear to me what "blocking" behavior you are worried about. All append
and remove operations are asynchronous so a UA is completely free to do the
"real work" on a separate thread if it wants to.
The example you give only defers the loading to a worker. The actual image
parsing and display still happens on the main thread so I'd be very surprised
if this actually results in a significant performance win. The main benefit I
can see by doing this would be that you would only try to display the image
once you know you have the whole thing instead of img tag taking up space when
it only has the image partially loaded.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 11 June 2014 16:01:43 UTC