13385 2011-07-27 11:28:33 +0000 Remove HTMLInputElement.{width,height} (unimplemented) 2011-10-21 22:38:36 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other CLOSED WONTFIX https://bugzilla.mozilla.org/show_bug.cgi?id=683855 http://www.whatwg.org/specs/web-apps/current-work/#the-input-element P3 normal --- 1 contributor ian ian mike mounir Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 51538 0 contributor 2011-07-27 11:28:33 +0000 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 53054 1 mike 2011-08-04 05:06:16 +0000 mass-moved component to LC1 54797 2 ian 2011-08-12 20:38:17 +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: 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. 54804 3 Ms2ger 2011-08-12 21:21:09 +0000 HTMLInputElement is a DOM interface, dammit. 55036 4 ian 2011-08-15 05:02:38 +0000 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. 55052 5 Ms2ger 2011-08-15 07:43:24 +0000 Doesn't matter much to me. Mounir? 55057 6 mounir 2011-08-15 08:43:55 +0000 (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. 56128 7 ian 2011-08-31 23:36:27 +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: Rejected Change Description: no spec change Rationale: Ok, I'm rejecting this on the basis that this is a new feature added for consistency. 56161 8 Ms2ger 2011-09-01 09:50:21 +0000 OK. 58667 9 ian 2011-10-21 22:38:36 +0000 Indeed, they were added in bug 6477.