New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some edit fields in firefox don't show their contents in a consistant manner. #4381
Comments
Comment 1 by jteh on 2014-08-12 10:03 Has this always happened for you? If not, when did it start happening? |
Comment 2 by driemer.riemer@... on 2014-08-12 18:08 |
Comment 3 by driemer.riemer@... on 2014-08-14 08:14 |
Comment 5 by jteh on 2014-08-24 08:52 |
Comment 6 by driemer.riemer@... on 2014-08-29 08:48 |
Comment 7 by driemer.riemer@... on 2014-08-29 08:51 |
Comment 8 by James Teh <jamie@... on 2014-09-12 04:04
|
Comment 9 by jteh on 2014-09-12 04:50 |
Comment 11 by driemer.riemer@... on 2014-09-12 05:33 |
Comment 12 by jteh (in reply to comment 11) on 2014-09-12 05:47
By much better, do you mean the problem is gone or it still happens occasionally but much less than it did? |
Comment 13 by driemer.riemer@... on 2014-09-12 06:56 |
Comment 14 by vgjh2005 on 2014-09-13 13:31 |
Comment 15 by jteh (in reply to comment 14) on 2014-09-13 21:10
The fix isn't in next yet. As noted in comment:9, I'm asking for feedback on a specific try build which I linked. |
Comment 16 by vgjh2005 on 2014-09-14 05:14 |
Comment 17 by lpintes (in reply to comment 9) on 2014-09-14 10:57 |
Comment 18 by jteh (in reply to comment 16) on 2014-09-14 11:02
The whole reason for this bug is that caret movement in Firefox 32 seems to have slowed down a little (perhaps because of MozillaBug:949518). |
Comment 19 by jteh (in reply to comment 17) on 2014-09-14 11:03
The fix isn't in master or next. It's in a separate branch (t4381). If you're seeing improvement in master, it's very likely placebo. |
Comment 20 by lpintes (in reply to comment 19) on 2014-09-14 11:48 |
Comment 21 by jteh on 2014-09-14 21:09 As to why master works for you when next doesn't, I can't think of any changes in next that should affect this. One possibility is that we actually wait longer for the caret to move in master because we handle unnecessary events (which we just drop in next), but that would suggest that some background app on your system is firing a lot of unnecessary events. |
Comment 22 by jteh (in reply to comment 21) on 2014-09-15 07:36
Actually, on further reflection, this doesn't make sense. Anecdotally, it does seem that next misbehaves more in this regard than master, but none of the currently incubating branches seem to suffer from this, so I have no idea why next might behave differently in this regard. |
Comment 23 by James Teh <jamie@... on 2014-09-16 03:10
|
Comment 24 by jteh on 2014-09-16 03:16 Lubos, thanks for the suggestion. You're most definitely right: it wasn't placebo, though it was quite tricky to figure out what was going on. I was under the impression that users had reported this with master or NVDA 2014.3, but I'm starting to think I was wrong. Has anyone experienced this with NVDA 2014.3 or master? |
Comment 25 by driemer.riemer@... on 2014-09-16 04:45 |
There may still be some rare instances of this, but the regression that caused this to be filed has been fixed. |
Reported by driemer.riemer@... on 2014-08-11 21:41
A good website to test this with is w3schools.com. On this site, if you click any of the examples, and try moving around in the editor with your html code, you hear unexpected results. This also happens in the editor window for tickets, which makes me think this happens in any multiline edit field.
Take this line for an example.
Sounds random when moved through with the arrows.
It one time may sound like <DDDTPMLL
And another time may sound like !OCTYYEhtml
This happens when moving by words as well.
This behavior is noticeable with regular English as well and is very prevalent on my machine on most websites.
It also happens when moving by line, and makes using multiline edit fields with nvda very hard if not impossibl with firefoxe.
Blocking #4412
The text was updated successfully, but these errors were encountered: