You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pay attention to the difference of caret positions before and after the tab switch(navigated back by browser history) when watching the following screen cast:
2023-03-12.12.46.09.mov
The positions were corrected after navigation because "go back" triggered a restoration turbo:visit where we added code for rerender logic. This issue should also exist in previous versions but it was not exposed because in previous version we also put data fetch process in xxxView.tsx so after data was fetched another setState() was triggered then the component rerendered again, which hid the issue from our eyes.
Expected Behavior
should be rendered in correct position as always.
Environment
- OS: whatever
- Browser: whatever
Any additional comments?
The issue is related to dynamic content of ReactTooltip v4. It seems v5 has a better solution, so we may have a try on v5.
The text was updated successfully, but these errors were encountered:
Version
1.9.0 (has not been released)
Current Behavior
Pay attention to the difference of caret positions before and after the tab switch(navigated back by browser history) when watching the following screen cast:
2023-03-12.12.46.09.mov
The positions were corrected after navigation because "go back" triggered a restoration turbo:visit where we added code for rerender logic. This issue should also exist in previous versions but it was not exposed because in previous version we also put data fetch process in
xxxView.tsx
so after data was fetched anothersetState()
was triggered then the component rerendered again, which hid the issue from our eyes.Expected Behavior
should be rendered in correct position as always.
Environment
Any additional comments?
The issue is related to dynamic content of ReactTooltip v4. It seems v5 has a better solution, so we may have a try on v5.
The text was updated successfully, but these errors were encountered: