Skip to content

react-dom: remove support for children content in <textarea/>#11639

Closed
raphamorim wants to merge 1 commit into
react:masterfrom
raphamorim:react-dom/remove-support-for-children-content-in-textarea
Closed

react-dom: remove support for children content in <textarea/>#11639
raphamorim wants to merge 1 commit into
react:masterfrom
raphamorim:react-dom/remove-support-for-children-content-in-textarea

Conversation

@raphamorim

@raphamorim raphamorim commented Nov 23, 2017

Copy link
Copy Markdown
Contributor

Let me know if I need to test/coverage some case.

@gaearon

gaearon commented Jan 5, 2018

Copy link
Copy Markdown
Collaborator

This is a breaking change so it'll need to be in React 17.
There should be a unit test that specifies what actually happens, yes.

@raphamorim

Copy link
Copy Markdown
Contributor Author

Ok, I'll work on it. :)

@gaearon gaearon added this to the 17.0.0 milestone Jan 5, 2018
@raphamorim raphamorim force-pushed the react-dom/remove-support-for-children-content-in-textarea branch 2 times, most recently from 57766b7 to 303ef84 Compare January 17, 2018 11:24
@raphamorim

Copy link
Copy Markdown
Contributor Author

@gaearon I update tests for this change.
Can you look it?

@raphamorim raphamorim force-pushed the react-dom/remove-support-for-children-content-in-textarea branch 2 times, most recently from 0f7c328 to 3def9fb Compare January 17, 2018 11:30
@raphamorim raphamorim force-pushed the react-dom/remove-support-for-children-content-in-textarea branch from 3def9fb to 51c084d Compare January 17, 2018 11:33
let children = props.children;
if (children != null) {
if (__DEV__) {
warning(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the warning should be kept (or converted into an error) in 17.0? I know that this is technically a breaking change that warns already, but having an explicit use value instead of children warning would avoid confusing debugging. Shouldn't be any perf impact if it's dev-only too, right?

@stale

stale Bot commented Jan 9, 2020

Copy link
Copy Markdown

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution.

@stale stale Bot added the Resolution: Stale Automatically closed due to inactivity label Jan 9, 2020
@necolas necolas added Resolution: Backlog Resolution: Stale Automatically closed due to inactivity and removed Resolution: Stale Automatically closed due to inactivity Resolution: Backlog labels Jan 9, 2020
@stale stale Bot removed the Resolution: Stale Automatically closed due to inactivity label Jan 9, 2020
@necolas necolas added the Resolution: Stale Automatically closed due to inactivity label Jan 9, 2020
@stale

stale Bot commented Jan 16, 2020

Copy link
Copy Markdown

Closing this pull request after a prolonged period of inactivity. If this issue is still present in the latest release, please ask for this pull request to be reopened. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed Resolution: Stale Automatically closed due to inactivity Type: Breaking Change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants