fix: Remove reliance on accidental behavior#8152
fix: Remove reliance on accidental behavior#8152dkennell wants to merge 1 commit intoreactjs:mainfrom
Conversation
|
Hi @dkennell! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
The initial call of
tickought to have a value for the 'now' argument' passed into it here. Currently, the code does work incidentally, but it passesundefinedintotick, with the result thatref.current.style.opacitygets set equal toNaN. The browser just ignores this, so nothing bad happens but it's fragile and could be confusing to readers. I suggest we passstartTimetotickwhen it's first called, so thatref.current.style.opacityjust gets set equal to 0 instead.