update dead jsx link to point to an extant page

syntax.html no longer exists, so point people at the in depth article instead.
put closing paren in correct place
remove dead link

the event handling doc page no longer exists
Send branch info from travis for continuous builds
Updated Changelog for 0.4.1
Blog post for v0.4.1
Updated Readme for 0.4.1
Change `ReactMultiChild` test to check for `innerHTML` descriptor.

Not all testing environments will support setting the `innerHTML` descriptor. For example, PhantomJS initializes the `innerHTML` property as not configurable.
Fix `Danger` test failures.

The original tests were flawed because the `Danger` module exploits the fact that all React-generated markup has at least one attribute. This allows the module to extract node names from markup strings faster.

However, the tests were passing in strings of markup with no attributes.

Also, this fixes a test failure due to the test trying to set text content into a `<tr>` which is typically disallowed by browsers (and PhantomJS). This changes it to use `<td>` instead.
Merge pull request #237 from yungsters/master

Fix Test Failures
Merge pull request #207 from thisishugo/patch-1

update dead jsx link to point to an extant page
Fix incorrect port of standard Python server

/ht @zpao
Merge pull request #241 from gasi/master

Fix incorrect port of standard Python server
Fix Reconciling Components to Content

This fixes a reconciliation bug introduced by adffa9b0f4128ca4832ddd03fdeca2c9fe434689.

The new unit test case exhibits the bug. When a component that has rendered child components is updated to render inline text, we usually:

 # Unmount and remove all child components.
 # Set the new inline text content.

However, with batched child operations, we do not **remove all child components** until later. The current implementation will set the inline text content and blow away those nodes, causing a fatal when `ReactMultiChild` later tries to find and remove those nodes.

This fixes the bug by ensuring that text content changes are also enqueued.
Get rid of initializeTouchEvents

We don't need it any more, thanks to @yungsters's 4deb0d61. Before that we weren't getting click events regardless of whether touch events were initialized, which was (as far as I know) the only thing to be worried about with this change.

Test Plan:
On an iPad, verified that a single element can receive touchstart, touchmove, touchend, mousedown, mouseup, and click events all at the same time (with a single tap, no less!).