RESOLVED FIXED 80101
[Forms] Make order of attribute/method in HTMLTextAreaElement.idl as same as specification
https://bugs.webkit.org/show_bug.cgi?id=80101
Summary [Forms] Make order of attribute/method in HTMLTextAreaElement.idl as same as ...
yosin
Reported 2012-03-01 22:20:22 PST
For ease of maintainability, attributes and methods declaration order should be as same as specification. http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-textarea-element Similar work was done for input element: https://bugs.webkit.org/show_bug.cgi?id=79622
Attachments
Patch 1 (3.30 KB, patch)
2012-03-01 22:24 PST, yosin
no flags
Patch 2 (3.25 KB, patch)
2012-03-01 23:17 PST, yosin
no flags
Patch 3 (3.45 KB, patch)
2012-03-02 00:18 PST, yosin
no flags
yosin
Comment 1 2012-03-01 22:24:29 PST
Kentaro Hara
Comment 2 2012-03-01 22:29:56 PST
Comment on attachment 129818 [details] Patch 1 View in context: https://bugs.webkit.org/attachment.cgi?id=129818&action=review > Source/WebCore/html/HTMLTextAreaElement.idl:61 > + // WinIE & FireFox extension: I am afraid this comment would be mis-placed by this change. Please be careful not to move comments randomly.
yosin
Comment 3 2012-03-01 22:39:30 PST
Attribute "labels" are now in specification. It is better to remove this obsolete comment not to make people confusing.
Kentaro Hara
Comment 4 2012-03-01 22:42:55 PST
(In reply to comment #3) > Attribute "labels" are now in specification. It is better to remove this obsolete comment not to make people confusing. I am confused. The comment "// WinIE & FireFox extension:" had been written on selectionStart, selectionEnd, selectionDirection, setSelectionRange() and setSelectionRange(), right?
yosin
Comment 5 2012-03-01 22:51:36 PST
Oops, sorry for confusion. Yes, comment "WinIE & FireFox extension" is above the "selectionStart" attribute, but I'm not sure this comments applied all of them. Anyway, all of them after comments, selectionStart, selectionEnd, selectionDirection and setSelectionRange are now in standard. IF this comment could be in line by line, e.g. attribute unsigned long selectionStart; // FF/IE extension attribute unsigned long selectionEnd; // FF/IE extension easier to understand.
Kentaro Hara
Comment 6 2012-03-01 22:54:57 PST
Comment on attachment 129818 [details] Patch 1 Makes sense!
Kent Tamura
Comment 7 2012-03-01 22:59:06 PST
Comment on attachment 129818 [details] Patch 1 View in context: https://bugs.webkit.org/attachment.cgi?id=129818&action=review > Source/WebCore/html/HTMLTextAreaElement.idl:64 > + // WinIE & FireFox extension: > #if defined(LANGUAGE_OBJECTIVE_C) && LANGUAGE_OBJECTIVE_C > void setSelectionRange(in long start, in long end); > #else setSelectionRange() isn't WinIE/FireFox extension, and should be below selectionDirection. http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html#the-textarea-element
yosin
Comment 8 2012-03-01 23:17:43 PST
yosin
Comment 9 2012-03-01 23:18:50 PST
Thanks tkent@ good catch! I remove "// WinIE & FireFox extension:"
Kent Tamura
Comment 10 2012-03-01 23:41:42 PST
Comment on attachment 129827 [details] Patch 2 View in context: https://bugs.webkit.org/attachment.cgi?id=129827&action=review > Source/WebCore/html/HTMLTextAreaElement.idl:55 > attribute DOMString selectionDirection; > + setSelectionRange should be here.
yosin
Comment 11 2012-03-02 00:18:37 PST
Kent Tamura
Comment 12 2012-03-02 01:02:20 PST
Comment on attachment 129834 [details] Patch 3 ok
WebKit Review Bot
Comment 13 2012-03-02 05:31:55 PST
Comment on attachment 129834 [details] Patch 3 Clearing flags on attachment: 129834 Committed r109565: <http://trac.webkit.org/changeset/109565>
WebKit Review Bot
Comment 14 2012-03-02 05:32:02 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.