-
Notifications
You must be signed in to change notification settings - Fork 47.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fixed removing attributes during custom element update. Fixes #6747 #6748
Fixed removing attributes during custom element update. Fixes #6747 #6748
Conversation
Looks good to me ( 👍 ) |
@jimfb Thanks for a such a quick review! I would really appreciate if you could let me know on the next steps so I can either setup our infrastructure around my fork, or wait for merge to master / next release. Thanks in advance. |
@grassator Merged into master. This should make it into one of the upcoming releases. |
@jimfb Thanks a lot for an expedited handling — it's really appreciated. |
node.removeAttribute(name); | ||
if (__DEV__) { | ||
ReactDOMInstrumentation.debugTool.onDeleteValueForProperty(node, name); | ||
ReactInstrumentation.debugTool.onNativeOperation( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: this method was renamed in #6754 which causes tests to fail now.
@gaearon sorry about that—I didn't know about upcoming rename. |
Yea, no problem! |
…k#6747 (facebook#6748) (cherry picked from commit 0e889d7)
Fix after facebook/react#6748 broke the monkey-patching
I've tried to follow the same approach as the
nextProps
takes, which involved adding a new method to explicitly delete the attribute without all the checks React does.I would be happy to any necessary changes and hope it can be merged soon.
Thanks
Fixes #6747.