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
{{ message }}
This repository has been archived by the owner on Aug 10, 2024. It is now read-only.
It renders a list that can be "navigated" by pressing Up and Down arrows. On a single keypress, next/previous element becomes active and current element becomes inactive.
Demo:
Each list element is rendered using render over correctly mapped KVar, and, as could be seen from websocket log, on single keypress only two affected list elements are updated. However, because changes to these two elements are applied one by one, it causes visible flicker (as could be seen on the gif above). I.e. there are rendered browser frames, when changes are applied partially, when one list element is removed, but not yet replaced by the new element.
This is different from how, for example, React + Mobx would behave.
To Reproduce
Run the linked example. Navigate list by pressing Up or Down arrow, observe flicker.
Expected behavior
Dom changes triggered by single KVar change should be batched and applied on the client within a single requestAnimationFrame.
The text was updated successfully, but these errors were encountered:
Describe the bug
Here is my minimal example: https://gist.github.com/Aivean/f4e7c0b15a860685f2eff7814b1ffa99
It renders a list that can be "navigated" by pressing
Up
andDown
arrows. On a single keypress, next/previous element becomes active and current element becomes inactive.Demo:
Each list element is rendered using
render
over correctly mappedKVar
, and, as could be seen from websocket log, on single keypress only two affected list elements are updated. However, because changes to these two elements are applied one by one, it causes visible flicker (as could be seen on the gif above). I.e. there are rendered browser frames, when changes are applied partially, when one list element is removed, but not yet replaced by the new element.This is different from how, for example, React + Mobx would behave.
To Reproduce
Run the linked example. Navigate list by pressing Up or Down arrow, observe flicker.
Expected behavior
Dom changes triggered by single KVar change should be batched and applied on the client within a single
requestAnimationFrame
.The text was updated successfully, but these errors were encountered: