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
Held down Ctrl + ] on the keyboard to request next page switching multiple times in a short period.
Observed pageNum changed from 1 -> 2 -> 3 -> 4 -> 3 -> 2 or a similar pattern where the view jumps back to a previous page although only "next" pages are requested.
The text was updated successfully, but these errors were encountered:
My intuition is that this is not fixed by #76, in normal use, we prevent this by locking the ui arrow buttons. I don't believe we provide the same support for key buttons. I will need to eventually confirm this with testing
Your intuition is right; it is true that we don't lock the key bindings during fast loading. But in state context provider, we are using pageNum for PREV_PAGE calculation, and the worst case is that we the keybinding triggers multiple PREV_PAGE calculation and loads the same page for a few times, which I think in this case is acceptable.
Bug
#54 added a Monaco editor instance and page switching can be achieved via keyboard shortcuts.
It was found that requesting the next page too frequently can cause the view to jump back to a previous page.
yscope-log-viewer version
fefbff7
Environment
Windows
Node.js 22 which runs the dev server
Microsoft Edge Version 129.0.2792.12 (Official build) stable app, beta channel (64-bit)
Reproduction steps
Ctrl
+]
on the keyboard to request next page switching multiple times in a short period.The text was updated successfully, but these errors were encountered: