GNOME Bugzilla – Bug 796333
in firefox, on click in web page, braille output is not moved
Last modified: 2018-06-27 19:12:35 UTC
Hello, When a sighted person uses the mouse to click within a line in a webpage, the braille output should move to there (and probably speech should tell e.g. the new context) More precisely, on a webpage just containing: <p>Some very very long text that can not fit within just one braille window, and thus scrolling is needed.</p> assuming that the caret is currently on word "Some", and the braille device is not long enough to show the whole sentence, if the sighted user clicks with the mouse on the word "needed", the braille output should show the end of the paragraph. Accerciser shows that firefox properly sends the text-caret-moved events, so I believe that orca already has all the required events? Oddly enough, moving the caret with arrows does make the braille output updated properly, so perhaps there is something special happening with mouse clicks? I made the priority minor since one can use arrows to get braille updated, the mouse would just be more convenient and intuitive. Samuel
Note: when clicking on another paragraph, braille is getting update appropriately. It's only when clicking somewhere else in the same paragraph that braille isn't getting updated. In the report above I mentioned clicking on a word not being shown on the braille device, but even when clicking on a word being shown, the braille caret should get updated to the new position, but it is not getting updated.
Fixed in master.