See http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#the-fieldset-element Adding "name" attribute to IDL is easy, because class HTMLFieldSetElement has disabled method inherited from HTMLFormControlElement.
Created attachment 129832 [details] Patch 1
Comment on attachment 129832 [details] Patch 1 View in context: https://bugs.webkit.org/attachment.cgi?id=129832&action=review > Source/WebCore/html/HTMLFieldSetElement.idl:24 > + attribute DOMString name; Please the specification carefully. http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#dom-fe-name This IDL attribute reflects the name HTML attribute.
(In reply to comment #2) > Please the specification carefully. Please read the ...
(In reply to comment #2) > > Source/WebCore/html/HTMLFieldSetElement.idl:24 > > + attribute DOMString name; > This IDL attribute reflects the name HTML attribute. I should have added more words. Sorry for the short comment. If the specification says the attribute "reflects" a content attribute, we should add [Reflect] to the IDL. Also, we need to add tests for the "reflect" behavior. e.g. fieldset.name = null, and check getAttribute('name') value.
Created attachment 129849 [details] Patch 2
Comment on attachment 129849 [details] Patch 2 WebKit has its own testing harness. Please consider to use it. See LayoutTests/fast/forms/ValidityState-customError.html for example.
Created attachment 130043 [details] Patch 3
Code looks good. Could you update the patch to match ToT?
Created attachment 130078 [details] Patch 4
Comment on attachment 130078 [details] Patch 4 Clearing flags on attachment: 130078 Committed r109836: <http://trac.webkit.org/changeset/109836>
All reviewed patches have been landed. Closing bug.