Facebook/react
1
0
Fork 0
mirror of https://github.com/facebook/react.git synced 2025-11-01 09:12:30 +00:00
Code Issues Packages Projects Releases Wiki Activity
4,098 Commits 681 Branches 148 Tags
aa6bfb6b5164d76b4e0497c0bcc4b7783b2eb38f
Commit Graph
1648 Commits
Author SHA1 Message Date
Jim b3c75d82b2 Merge pull request #3521 from grant/master 
Display error when trying to create an element of type `boolean`. Fixes #3478
 2015-03-26 14:39:32 -07:00
Mert Kahyaoğlu 6248406d6a remove unrelated doc line 2015-03-26 21:08:32 +02:00
Grant Timmerman 59a914aac0 Disable numeric element types 2015-03-26 10:07:56 -07:00
Grant Timmerman 3c9ea72795 Display error when trying to create an element of type boolean. Fixes #3478 2015-03-26 01:21:54 -07:00
Ben Alpert b32fbef7c5 Add missing semicolon 2015-03-25 18:10:49 -07:00
Ben Alpert 7c6694987d Tweak validation message, add html support 
The old message made no sense if you had a > div > a or similar. I'm clearly feeling sloppy today.
 2015-03-25 17:24:13 -07:00
Ben Alpert 07b7e8424d Remove stray console.log comment 2015-03-25 17:06:42 -07:00
Ben Alpert 76bb96ef21 Validate only against problematic tag nesting 
Turns out lots of people write invalid HTML all the time and no one, including your browser or React, cares. Most invalid HTML combinations don't cause magic reparented nodes; only some do. The HTML5 parsing spec (https://html.spec.whatwg.org/multipage/syntax.html) specifies which tag combinations cause strange parsing behavior. I did my best to encode the logic here. It's more lenient than before in some cases, but more strict in others (before we didn't look at the whole stack of tags; now we warn with deeply nested `p` or `form` or `a` tags).
 2015-03-25 16:43:41 -07:00
Paul O’Shannessy 27a191e704 Merge pull request #3513 from agelter/master 
Added support for the 'low', 'high', and 'optimum' attributes that are missing from the <meter> tag.
 2015-03-25 12:17:07 -07:00
Paul O’Shannessy 56b180b464 Fix failing test 
PR #3494 was based on master before we shifted to using console.error. This
just fixes the new test case.
 2015-03-25 12:15:41 -07:00
Jim 13dbda3644 Merge pull request #3494 from letiemble/B_Context_Rerender 
Fix the context handling when updating a rendered component.
 2015-03-25 11:55:35 -07:00
Aaron Gelter c9e82ce0f6 Added support for the 'low', 'high', and 'optimum' attributes that the <meter> tag requires. 2015-03-25 11:33:02 -06:00
Damien Pellier 3d45c0ad9d add scoped property to the list of DOM standard properties 2015-03-25 09:41:05 +01:00
Paul O’Shannessy 09ecf8bca9 Merge pull request #3499 from sverrejoh/patch-1 
Don't add 'px' to strokeDashoffset CSS Properties
 2015-03-24 13:57:02 -07:00
Sverre Johansen 77abea5ddc Reordered properties to maintain ABC order 2015-03-24 20:43:55 +00:00
Ben Alpert 6ad4afd404 Merge pull request #3502 from spicyj/tests 
Fix tests after merge of #3440
 2015-03-24 13:41:34 -07:00
Paul O’Shannessy 2795fb162a Merge pull request #3490 from chenglou/remove-class-addon 
Remove classSet/cx
 2015-03-24 13:39:47 -07:00
Ben Alpert 4dde417214 Fix tests after merge 
Test Plan: jest
 2015-03-24 13:37:39 -07:00
Ben Alpert 9260b540ad Merge pull request #3467 from spicyj/valid-3 
Validate node nesting, take 3
 2015-03-24 13:30:16 -07:00
Ben Alpert 1aa4e3c234 Merge pull request #3440 from spicyj/console-error 
Use console.error to show stack trace in console
 2015-03-24 13:30:01 -07:00
Sverre Johansen c28059e39b Don't add 'px' to strokeDashoffset CSS Properties 
This is a SVG CSS Property. The standard expects values or percentages, and adding "px" to the value will break it.

http://www.w3.org/TR/SVG/painting.html#StrokeDashoffsetProperty
 2015-03-24 17:52:02 +00:00
Laurent Etiemble 357345a56d Fix the context handling when updating a rendered component. 2015-03-24 08:29:09 +01:00
Cheng Lou 18ab88aa78 Remove classSet/cx 2015-03-23 17:59:27 -04:00
Ben Alpert f9abf493b4 Validate node nesting, take 3 
Nicer version of #644 and #735. Fixes #101. Context is neat.
 2015-03-20 16:10:02 -07:00
Mert Kahyaoğlu 63aa7259b9 move getReactRootElementInContainer to ReactMount.js 
getReactRootElementInContainer.js file contains one function used only
in ReactMount.js.
 2015-03-20 20:50:11 +02:00
Mert Kahyaoğlu 0c1eca7dfc fix doc comments and typos 2015-03-20 18:21:29 +02:00
Ben Alpert 7fe5a3aadd Merge pull request #3442 from spicyj/kill-initializeTouchEvents 
Kill React.initializeTouchEvents for good
 2015-03-19 14:15:26 -07:00
Ben Alpert a321247ee5 More lint fixes 2015-03-17 14:17:03 -07:00
Ben Alpert 26664315a6 Merge pull request #3438 from spicyj/lint 
Lint fixes
 2015-03-17 14:14:57 -07:00
Ben Alpert 9c4c2f58ea Kill React.initializeTouchEvents for good 
Now that #1169 is fixed, the only thing this is used for is to determine whether `onTouchTap` causes touch listeners to be added. The only internal uses of TapEventPlugin are where touch events are already initialized (so this doesn't make a difference) and we don't support `onTouchTap` as part of the public API so this should be safe.
 2015-03-17 14:12:26 -07:00
cpojer fb23276178 Add warning for getDOMNode calls. 2015-03-17 14:08:04 -07:00
Ben Alpert e791fccf58 Use console.error to show stack trace in console 
Better version of #3277.

Test Plan: jest, grunt test
 2015-03-17 13:39:04 -07:00
Ben Alpert c34fa7f3d2 Lint fixes 2015-03-17 13:30:15 -07:00
Ben Alpert 9a6fa5eb7d Merge pull request #3430 from fourcolors/patch-1 
fix grammar in comments
 2015-03-17 11:08:40 -07:00
Mihai Parparita 60a101eced Include the owner name when warning about createElement(null/undefined). 
Makes it easier to find the callsite that needs to be fixed.
 2015-03-16 22:05:29 -07:00
Sebastian Markbage 50cbdbc9ab Don't use owner to determine statefulness 
This reverts an early commit that made it so that elements from two
different owner in the same slot wouldn't share state.

That behavior was helpful, and we did hit a case which was solved by this.
However, this pattern is extremely uncommon. I've yet to even find the
original case, let alone any existing cases in our codebase.

Therefore, we're dropping this to simplify elements and enable new
optimizations.
 2015-03-16 18:05:15 -07:00
Jim 12059299f3 Added webcomponents.js and a simple unit test verifying a document fragment as a valid React container. 2015-03-16 16:37:05 -07:00
Jim 73f4dc59d8 Merge pull request #3169 from jsfb/mount-into-shadowdom 
Allow rendering into document fragments. Fixes #840
 2015-03-16 16:15:03 -07:00
Paul O’Shannessy 10112672b1 Merge pull request #3395 from Simek/reactComponentExpect-cleanup 
toBeDOMComponentWithChildCount readability
 2015-03-16 16:14:48 -07:00
Sterling Cobb b59e7e60b5 fix grammer in comments 2015-03-16 17:10:14 -06:00
Paul O’Shannessy 99cbaed836 Ensure FullPageComponents are treated as DOM components 
We currently override a couple DOM components. We need to ensure everything we
override is still treated as a DOM component, even if it has a composite
component wrapper.
 2015-03-16 15:18:39 -07:00
Paul O’Shannessy 93e67a0a5b Merge pull request #3425 from zpao/fix-pure-test 
Fix PureRender test to use providesModule
 2015-03-16 15:14:26 -07:00
Ben Alpert 0a312bba89 Merge pull request #3414 from spicyj/gh-3407 
Fix up Perf a bit better for 0.13
 2015-03-16 14:04:28 -07:00
Paul O’Shannessy bb0fc28fac Fix PureRender test to use providesModule 2015-03-16 13:56:43 -07:00
Austin Wright 29416f422e Appease eslint 2015-03-14 14:08:18 -07:00
Austin Wright b52bb22342 Move list of newline-eating tags to variable 2015-03-14 13:57:15 -07:00
Austin Wright 030a7b34c7 Add back \n-to-be-eaten for the plain-text elements 
The comment hack to enable polyglot HTML isn't cross-browser, or simply doesn't work.
 2015-03-14 13:53:12 -07:00
Austin Wright 8e714f9898 Update tests to use Polyglot profile of HTML 2015-03-14 13:53:12 -07:00
Austin Wright e913e85e1a Use a Polyglot HTML-safe method of escaping leading newline in rawtext elements 2015-03-14 13:53:12 -07:00
Austin Wright 8bc828aa7c Generate XML-compatible tags and boolean attributes 2015-03-14 13:53:12 -07:00