[Forms] The "progress" element should not be a form-associated element.

According the specification, the "progress" element isn't a form-associate element.
http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#form-associated-element

However, current implementation of HTMLProgressElement is derived from HTMLFormControlElement. We have unexpected dependency between HTMLProgressElement and HTMLFormControlElement and FormAssociatedElement. Also, We waste time in loop of HTMLFormElement::m_associatedElements.

For clear understanding and better maintainability, it is better that C++ class hierarchy should be similar to specified in the specification.

This bug is part of HTMLFormControlElement re-factoring meta bug https://bugs.webkit.org/show_bug.cgi?id=80381

Created attachment 132228 [details]
Patch 1

[Kent Tamura]

Comment on attachment 132228 [details]
Patch 1

View in context: https://bugs.webkit.org/attachment.cgi?id=132228&action=review

> Source/WebCore/ChangeLog:10
> +        extra "meter" elements in HTMLFormElement::m_formAssociatedElements

This is not a "meter"

Created attachment 132240 [details]
Patch 2

(In reply to comment #3)
> (From update of attachment 132228 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=132228&action=review
> 
> > Source/WebCore/ChangeLog:10
> > +        extra "meter" elements in HTMLFormElement::m_formAssociatedElements
> 
> This is not a "meter"

Oops, I forgot to update this one... orz

[Kent Tamura]

Comment on attachment 132240 [details]
Patch 2

ok

[WebKit Review Bot]

Comment on attachment 132240 [details]
Patch 2

Clearing flags on attachment: 132240

Committed r111009: <http://trac.webkit.org/changeset/111009>

[WebKit Review Bot]

All reviewed patches have been landed.  Closing bug.