Add per-app scroll source ignore option#939
Conversation
Allow per-application entries to bypass Mos scroll handling when the app itself emits a scroll event. This keeps keyboard scrollers from being smoothed or accelerated while preserving existing target-app settings.
|
why we need this? |
|
Applications that support keyboard-based scrolling (such as Homerow and Keyboard Scroller) generate scroll events that Mos intercepts, often resulting in excessive scrolling. Since these apps typically include their own smooth-scrolling functionality, using Mos alongside them can cause conflicts. |
|
Hi @MahdiNazemi , thanks for your explanation This scenario seems uncommon, but the implementation strategy is correct. My consideration was to avoid increasing the performance overhead of the scrolling process with such rare use cases (the overhead of each if-else statement in the core scrolling module's pipeline is amplified). The interactions and styles under Application pagination also need to be considered, since Target and Source are two different semantics. If more users report similar issues, I will consider merging this MapReduce and further optimizing the UX |
Summary
Testing