https://bugs.documentfoundation.org/show_bug.cgi?id=109398
--- Comment #19 from Joanmarie Diggs <jdi...@igalia.com> --- (In reply to Chris Sherlock from comment #18) > Joanmarie, can you give us some hints as to what the workaround actually > does? What do you think might be causing this? A few of us have tried to > reproduce the issue, but we just aren't having much luck. In default.py, onCaretMoved checks to see if the object firing the caret-moved event exposes STATE_SHOWING. If STATE_SHOWING is absent, then that event is ignored because we only want to (potentially) present the new caret location if the user is in that text object. And if the thing isn't SHOWING, presumably the user is not in that text object. The workaround is the addition of presentEventFromNonShowingObject, which allows scripts to tell the default script that even though something isn't SHOWING, the caret moved event might still be worthy of presentation. The default implementation of presentEventFromNonShowingObject returns False. The LO script's implementation unconditionally returns True. As for what I think might be causing this on the LO side of things, my guess would be either the logic which determines if a paragraph is SHOWING and/or the logic which updates (via a state-changed accessibility event) the SHOWING state (e.g. when something is scrolled into or out of view). -- You are receiving this mail because: You are the assignee for the bug.
