- From: <bugzilla@jessica.w3.org>
- Date: Thu, 07 Oct 2010 19:59:42 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9895
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |adrianba@microsoft.com,
| |annevk@opera.com,
| |ap@webkit.org,
| |eric@webkit.org,
| |mjs@apple.com,
| |tdillon25@gmail.com,
| |zcorpan@hotmail.com
--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-07 19:59:42 UTC ---
Requiring that drawImage() become synchronous in certain cases seems
suboptimal.
Do other browser vendors have an opinion here?
It's not really clear to me what the best solution is here. Obviously requiring
that all images downloaded get decoded even if they're never used is a poor
choice. Can we consider decoding images synchronously to be instantaneous, and
thus make drawImage() do that safely?
I guess, in the absence of requests to the contrary, that I will update
complete to be defined in terms of having all the data immediately available,
but not having checked whether the image can be decoded; I'll then clarify
drawImage() and .height/.width to support the case of the image decoding
happening on request and say how to handle errors in those cases.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 7 October 2010 19:59:44 UTC