https://bugs.documentfoundation.org/show_bug.cgi?id=169742
Eyal Rozenberg <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Eyal Rozenberg <[email protected]> --- (In reply to Buovjaga from comment #3) > Adding perf keyword per discussion in dev chat (we don't need such > aggressive debouncing tactics anymore). So, there are actually several questions to ask here: 1. Should we have "debouncing" / delayed reaction at all? 2. If we have debouncing, how long should it be for? 3. Should "debouncing" be continously re-triggerable by actions such as typing (and thus, potentially, infinite)? I'm sure the answer to (3.) is negative. Once we've started counting some delay, we should not reset that counter; the UI should be recomputed/repainted/updated after that timeline expires, even if an additional debounce-triggering event occures. About questions (1.) and (2.) I am not too sure. But - I would think that this should depend on how fast the machine we're running on actually is, and perhaps what load level it's under. If that's at all possible to check. I leave that part to the capable hands of the developers. > When some area gets heavy interaction, it does not make sense > to spend CPU time in real-time monitoring. But maybe the behaviour can be > tweaked without harming performance. There is also the question of what constitutes "heavy interaction". Is typing text after having typed Enter, in an otherwise empty document, heavy interaction? -- You are receiving this mail because: You are the assignee for the bug.
