14036 2011-09-05 21:43:47 +0000 WF2: Make HTMLInputElement.width and HTMLInputElement.height work like <img>'s .width and .height 2011-10-28 00:11:52 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED FIXED P2 normal --- 1 bugs ian annevk ian me mike mounir public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 56348 0 bugs 2011-09-05 21:43:47 +0000 56396 1 mounir 2011-09-06 15:54:59 +0000 FWIW, IE [1] is the only browser I've found implementing these two attributes and there are reflected as number, not string. [1] Tested with version 9 only. 57933 2 annevk 2011-10-07 09:34:59 +0000 Do they also have the additional magic that width/height on <img> have? 58668 3 ian 2011-10-21 22:42:01 +0000 They're DOMString because historically they've been able to take percentages, too. Note that these attributes are new (see bug 6477), so be wary when testing UAs. I guess I can change them to unsigned long if people think that's a good idea? I don't really care either way here. 58683 4 annevk 2011-10-22 00:42:02 +0000 Opera recently added them (not sure if shipping) and we decided to make them behave the same way as <img>, including the rendered height/width bit. Making <input type=image> and <img> alike seems like a good idea to me. 58732 5 mounir 2011-10-24 10:31:44 +0000 (In reply to comment #4) > Making <input type=image> and <img> alike seems like a good idea to me. I agree. It's probably more convenient for authors if the behavior of those attribute is consistent between elements. 59111 6 ian 2011-10-27 23:55:23 +0000 Seems reasonable. Will do. 59112 7 ian 2011-10-28 00:11:12 +0000 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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 59114 8 contributor 2011-10-28 00:11:52 +0000 Checked in as WHATWG revision r6775. Check-in comment: Define input.width and input.height. http://html5.org/tools/web-apps-tracker?from=6774&to=6775