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
You can imagine the app is like a spreadsheet app.
You can recognize that low priority updates block high priority updates.
I guess that will become a huge problem with IME composition events.
(Try to type "こんにちは(konnnitiha)")
The previous version that used requestIdleCallback didn't have the problem.
Because requestIdleCallback runs a registered callback only when the UI thread is idle.
The following is a version that uses requestIdleCallback.
TimeSlicing is a great feature, thank you for your great works!
I've been enjoying it, but I have a problem with its scheduling.
I know the scheduler is unstable, this issue is just to tell you a prblem I have.
The problem:
If I have high priority updates and many low priority updates, low priority updates interrupt and block the high priority updates.
How to reproduce:
You can imagine the app is like a spreadsheet app.
You can recognize that low priority updates block high priority updates.
I guess that will become a huge problem with IME composition events.
(Try to type "こんにちは(konnnitiha)")
The following is a timeline I've measured.
The source code is here.
https://github.com/koba04/react-timeslicing-demo
The previous version that used requestIdleCallback didn't have the problem.
Because requestIdleCallback runs a registered callback only when the UI thread is idle.
The following is a version that uses requestIdleCallback.
https://react-timeslicing-demo.netlify.com/
Should I implement another way to avoid to block high priorities by low priorities?
The text was updated successfully, but these errors were encountered: