- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Dec 2010 23:31:13 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11459
Summary: "If the image argument is an HTMLImageElement object
that is not fully decodable ... then the
implementation must return without drawing anything."
This is terrible! It completely prohibits displaying
images incrementally. When I'm loading a 5 MB 3000x3
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#ima
ges
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: HTML Canvas 2D Context (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
Specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#images
Comment:
"If the image argument is an HTMLImageElement object that is not fully
decodable ... then the implementation must return without drawing anything."
This is terrible! It completely prohibits displaying images incrementally.
When I'm loading a 5 MB 3000x3000 image, not being able to draw
partially-loaded images is a serioius problem. If an image isn't fully
loaded, allow (don't require) UA's to blit what data is available. Don't
preemptively destroy all progressive loading!
Posted from: 76.24.235.31
--
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, 2 December 2010 23:31:16 UTC