<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [Feature] Follow Editor" href="https://bugs.documentfoundation.org/show_bug.cgi?id=108341#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [Feature] Follow Editor" href="https://bugs.documentfoundation.org/show_bug.cgi?id=108341">bug 108341</a> from <a class="email" href="mailto:pranavk@collabora.co.uk" title="Pranav Kant <pranavk@collabora.co.uk>"> Pranav Kant</a> <pre>(In reply to Jan Holesovsky from <a href="show_bug.cgi?id=108341#c4">comment #4</a>) > Wrt. the automatic switching - I think easiest would be that when there is a > lag in typing [2-5 seconds maybe?], consider that a switch time, and then > whoever starts typing first after that lag, he/she is the chair until the > next lag :-) And do you mean handling this in online.git only ? I am not sure about its reliability if we handle this in online.git only. For example, a user hitting an arrow key repeatedly to navigate into the document can become an editor unless we handle all of such cases in loolwsd to distinguish between printable and non-printable keys. But at the same time, taking it to core.git might be making the LOK API unnecessarily complex - I imagine some callbacks to notify the LOK clients and then some code to detect that user typed something.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>