svg properties -> attributes
svg: rx/ry for rounded corners
svg attributes properly cased when assigned by react
DefaultDOMPropertyConfig: sort properties alphabetically
Merge pull request #419 from piranha/svg-attrs

svg properties -> attributes

Fixes #190
Forcibly wrap SVG nodes with <svg> on creation

Forcing wrapping seems necessary here: I compared a <circle> created within a <div> with a <circle> created inside an <svg> and they appear to have exactly the same properties with the exception of .parentNode (and .parentElement), yet the former refuses to show up when appended to an <svg> element. As such, I can't find any useful way to write a unit test (testing getMarkupWrap's output doesn't seem particularly useful to me).

Fixes #311.

Test Plan:
With a component that adds a <circle> after mounting (such as http://jsfiddle.net/spicyj/hxFVe/), verify that the circle appears in both Chrome and IE9.
[docs] Fix a broken link to JSX syntax in README.
#JSX => #jsx
Add bitwise lint escape to DefaultDOMPropertyConfig
Ensure attribute values are strings

`jsdom` behavers differently than browsers here and we should ensure
that we are consistent. Browsers should be (and are) converting to
a string first, while `jsdom` doesn't.
Standardize prop -> DOM attribute process

Allow more than strings and numbers to be used as attributes for DOM
nodes. This removes the special casing for `0` and `false` that was
being used in ReactDOMInput and ReactDOMTextarea.

Now we will just `toString` any object we try to insert into a DOM.

Closes #422, #372, #302
Be consistent with object naming in tests

This also fixes line length issues our linter was complaining about.
Make sure DOM components work in JSDOM
Merge branch 'SanderSpies-sspi-dom-attribute-process'
Merge pull request #426 from SanderSpies/sspi-fix-jsx-doc-link

In-browser JSX warning linked to wrong anchor (should be lowercase)
new addons docs

closes #403
Updated AUTHORS for 0.5

closes #414
Fix Lint

Enabling bitwise linting caught another user. Also fixed a semicolon
misuse.
Use getActiveElement module

We had something that did the same sort of protection. The module
differs slightly (returns document.body instead of undefined) but
looking at the callers, that should be ok.
Enable linting for bitwise operators