Next snapshot ignoring browse mode settings in search edit fields like google or startpage #7323
Assignees
Labels
Comments
jcsteh
added a commit
that referenced
this issue
Jun 26, 2017
…sed by c967b21. Firefox fires caret events even when you use caret movement commands when already at the edge of the control. That means we don't fire caretMovementFailed events in these cases. Furthermore, it seems quite a few things (e.g. Wordpad, Notepad++) don't fire valueChange or caret events when you press delete. To work around this, drop the checks for caret and valueChange events (and revert the shouldAllowSystemCaretEvent stuff). Instead, when pressing delete, compare the word at the caret (in addition to bookmarks) to detect movement.
|
Hi tried it on my windows 7 box and all seems well.
Still playing with the hanging thing, it seems to have gone away again at
the movement.
Brian
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using latest next downloaded on 24th June 17, when options in brows mode set to allow cursoring through edit fields so you can hear focus and browse mode changes, this particular snap when usedwith firefox 54 and earlier only lets you out of edit with cursor left. all other directions result in no movement, though you can tab out.
Normal web site form fields seem to be unaffected.
This was tested on windows 7 64 with 32 bit Firefox and also Windows xp, both portable and installed.
Earlier snaps in Next are not affected. Master is not affected.
Automatic focus mode for focus changes
Automatic focus mode for caret movement
both checked
The text was updated successfully, but these errors were encountered: