Fix a small typo
Update api docs for shape data attribute.
Graphics build files. No mins.
API Doc changes for 3.6.1 -> 3.7.0 (builds to follow in subsequent commit)
3.6.1 -> 3.7.0 in HISTORY.mds
Build for APIDoc 3.6.1 -> 3.7.0. No -min files were hurt in the making of this commit point
Added subscribers/afters deprecated note to event-custom landing page
Updates to data attribute api docs
Graphics build files. No mins
Fixed capitalization in api docs for canvasshape and vmlshape.
Graphics build files. No mins.
src/graphics/docs/index.mustache
Merge remote-tracking branch 'upstream/master'
Merge branch 'graphicdocsupdate'
Update graphics user guide api docs links.
Merge branch 'graphicdocsupdate'
Fix copy/paste and spelling errors in `node-scroll-info`'s API docs.
Build node-scroll-info. No -min changes.
Merge branch '3.x' of yuisource.corp.yahoo.com:yui3 into 3.x
IE10 Get issues. WIP

There seems to be 2 issues with IE10 and Get support:

a) IE10 seems to interrupt an executing JS thread, when an onload is recieved,
   in certain circumstances (304 with async:true?).

   This was causing the onSuccess to be fired early, since we'd be iterating
   the request loop, and if the first file was a 304, the loop would get
   interrupted, _waiting would be 1, since all the request nodes hadn't been
   inserted yet, and the onload for the 304 would knock waiting down to 0,
   and call the onSuccess handler prematurely.

   The right fix for this regardless of the IE10 behavior seems to be
   to maintain a count of the expected responses for the transaction,
   independent of how many nodes have been added. We can then count down,
   as progress is made as we used to before, and things should be
   good with or without the IE10 interrupt behavior. The transaction
   is only complete when we recieve the expected responses (success or
   failure).

   I haven't been able to repro the "interrupt" behavior outside of Get
   yet which worries me a little though.

b) After issuing a Get transaction for 2 of the same urls, which 404,
   the next Get transaction, with a valid url doesn't invoke the onload
   handler (or the error handler for that matter).

  This seems like a straightup IE10 issue, but need to whittle it down.

This commit has the fix for a), and some standalone repro cases I'm working
with.