This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8661 - Contradiction of dimension attributes
Summary: Contradiction of dimension attributes
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: a11y
Depends on:
Reported: 2010-01-06 11:23 UTC by Gez Lemon
Modified: 2010-10-04 14:33 UTC (History)
4 users (show)

See Also:


Description Gez Lemon 2010-01-06 11:23:56 UTC
Item 8 says, "For historical reasons, the coordinates must be interpreted relative to the displayed image, even if it stretched using CSS or the image element's width and height attributes."

This appears to contradict section 4.8.17, which says, "The dimension attributes are not intended to be used to stretch the image." Is the use of width and height to stretch an image conforming?
Comment 1 Ian 'Hixie' Hickson 2010-01-07 11:53:28 UTC
Yes and no. The exact authoring conformance criteria in this particular case are somewhat convoluted, and take up most of the "Dimension attributes" section. It's "yes" because displaying the image "unstretched" (from the user's perspective) might involve "stretching" it (from a technical perspective), if, e.g., the image resolution is not 96ppi. But it's "no" because you can't change the ratio. (It's also "yes" because you can "stretch" the image to 0x0.)

I hope this clarifies matters... I fear it may not have. :-)

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

Status: Rejected
Change Description: no spec change
Rationale: I'm marking this "Rejected" because I didn't make any change to the spec. Please let me know if I misunderstood what you were saying.
Comment 2 Michael Cooper 2010-02-11 17:26:38 UTC
Per the proposal at, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future.