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 13385 - Remove HTMLInputElement.{width,height} (unimplemented)
Summary: Remove HTMLInputElement.{width,height} (unimplemented)
Status: CLOSED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-27 11:28 UTC by contributor
Modified: 2011-10-21 22:38 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2011-07-27 11:28:33 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html
Multipage: http://www.whatwg.org/C#the-input-element
Complete: http://www.whatwg.org/c#the-input-element

Comment:
Remove HTMLInputElement.{width,height} (unimplemented)

Posted from: 91.181.30.149 by ms2ger@gmail.com
User agent: Mozilla/5.0 (X11; Linux i686; rv:7.0a1) Gecko/20110613 Firefox/7.0a1
Comment 1 Michael[tm] Smith 2011-08-04 05:06:16 UTC 
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-12 20:38:17 UTC 
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:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: They're... not unimplemented. Do you have a test case showing what you mean? These seem to work in every browser I've tested.
Comment 3 Ms2ger 2011-08-12 21:21:09 UTC 
HTMLInputElement is a DOM interface, dammit.
Comment 4 Ian 'Hixie' Hickson 2011-08-15 05:02:38 UTC 
So I was about to remove these, when I pondered... don't we _want_ them to be implemented? I mean, why omit just these two? It seems weird.
Comment 5 Ms2ger 2011-08-15 07:43:24 UTC 
Doesn't matter much to me. Mounir?
Comment 6 Mounir Lamouri 2011-08-15 08:43:55 UTC 
(In reply to comment #5)
> Doesn't matter much to me. Mounir?

I don't care that much but I would tend to think we should keep those attributes in HTMLInputElement. The content attributes apply to img, iframe, object, embed, video and <input type=image>, I don't see any reason to have the IDL attributes not applying to the exact same set of elements.
Comment 7 Ian 'Hixie' Hickson 2011-08-31 23:36:27 UTC 
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:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Ok, I'm rejecting this on the basis that this is a new feature added for consistency.
Comment 8 Ms2ger 2011-09-01 09:50:21 UTC 
OK.
Comment 9 Ian 'Hixie' Hickson 2011-10-21 22:38:36 UTC 
Indeed, they were added in bug 6477.