Sidetracking whether chaining is a useful API design or not isn't useful.
Choosing some mechanism to add multiple classes at once is useful, whether
that's making add have an arbitary arity, allow it to take an array, allow
it to take a space seperated string or allowing add calls to be chained.
Personally as a web developer this a feature of forms that I've missed when
I'm building my REST apis and then have to put in some kind of hidden input
for method overwrite.
I know of other developers that also agree that this is a wanted feature.
On Wed, Feb 22, 2012 at 5:38 PM, Adam Barth
http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#dom-form-nameditem
says to return a live NodeList
where as
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#dom-htmlformcontrolscollection-nameditem
says to return a RadioNodeList
This
With less sarcasm: What use is this if one already reads the blog?
None, this isn't for you. It's for people who use G+. It's a minor addition
that increases the total number of ways you can get information.
As long as G+ is only an optional addition for people who want to use it,
does it
