From 3bbd966a829b10285fbf9548b280f05ca2a45543 Mon Sep 17 00:00:00 2001
From: Ben Alpert <spicyjalapeno@gmail.com>
Date: Mon, 9 Sep 2013 18:44:36 -0700
Subject: [PATCH] Fix radio input test in Chrome

It seems like the `form="pluto"` was throwing it off and making the input live outside the form it should have been contained in, causing it to uncheck A. I added it intending to test the form attribute but ended up not needing it so removing it should be fine. (The tests were passing in phantomjs since it doesn't support the `form` attribute and simply ignored it.)

Test Plan:
grunt test; grunt test --debug
---
 src/dom/components/__tests__/ReactDOMInput-test.js | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/dom/components/__tests__/ReactDOMInput-test.js b/src/dom/components/__tests__/ReactDOMInput-test.js
index 1b9f7d542f..ebb845213a 100644
--- a/src/dom/components/__tests__/ReactDOMInput-test.js
+++ b/src/dom/components/__tests__/ReactDOMInput-test.js
@@ -61,8 +61,7 @@ describe('ReactDOMInput', function() {
             <input ref="b" type="radio" name="fruit" />B
 
             <form>
-              <input ref="c" type="radio" name="fruit" form="pluto"
-                defaultChecked={true} />
+              <input ref="c" type="radio" name="fruit" defaultChecked={true} />
             </form>
           </div>
         );