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
firefox edit fields: duplicate llines and words #3156
Comments
Comment 1 by jteh on 2013-04-15 22:20
It'd be good if you could confirm this fits your first issue. As for the issue regarding duplicate words, I'm not sure about this one, though it may relate to an issue with Firefox when there is punctuation near the current word. This might give you some idea how to reproduce this reliably. If you do find a way to reproduce it reliably, please comment. |
Comment 3 by camlorn on 2013-04-16 02:17 |
Comment 4 by camlorn on 2013-04-26 01:32 |
Comment 5 by jteh on 2013-04-26 01:56 As for duplicate lines, I still suspect what I said in comment:1 about the position at the end of the line. If you see duplicate lines again, press home and see if it goes away. Note that contrary to my comment, it seems that pressing end isn't the only way to reproduce this. I suspect you can land on the end of line position if your position in the current line is after the end of the previous line; i.e. the previous line is shorter. |
Comment 6 by a11cf0.vk on 2013-05-11 12:27 |
Comment 7 by jteh on 2013-06-07 05:53 @camlorn, it'd be good if you can give this try build a spin to see if it fixes your repeated lines issue: I also filed MozillaBug:880159 to make character and word reporting more appropriate at the end of a line. |
Comment 8 by jteh (in reply to comment 6) on 2013-06-07 05:54
This is unrelated to this ticket. It might be #2039. |
Comment 9 by jteh (in reply to comment 7) on 2013-06-25 07:34
For character, our current proposal is that Mozilla should return a collapsed range. I just tested whether that would work in NVDA. It does say "blank". However, the problem is that move(UNIT_CHARACTER, 1) won't move past that point. I don't think this affects any current code, but it's probably still bad. Mick, thoughts? |
@jcsteh I guess this is still an issue in last Firefox version. Right? |
This issue still exists, yes. However, the necessary changes need to be made in NVDA, not Firefox. The relevant Firefox bug is now fixed. |
Starting to understand this issue.
Actual:
Expected:
"Hello, Fine And you? " |
Maybe it's less common but it remains a bug. There is no reason to close; it may just be considered lower priority if it is less common. Personally, I am using word by word nav, but also home/end. |
Personally, I am using word by word nav, but also home/end.
I do not usually use pgUp or pgDown in focus mode, but maybe others do, e.g. people using web apps such as editors.
Same for me. I use home/end all the time in text fields and textareas.
|
There is still an issue in both Chrome and Firefox where if you're positioned at the end of a wrapped line, NVDA will report the next line instead of the current line. STR:
Firefox at least supports the necessary IAccessible2 stuff to make this work correctly, but NVDA doesn't support it yet. I don't think Chrome does, but I'm not sure.
I don't think this is correct. Different browsers have slightly different word navigation behaviour. That's not something NVDA should try to change. That said, the browse mode behaviour is not going to be consistent with focus mode word navigation and I don't think that's important.
I'm not sure what you mean about Firefox repeating punctuation here. Can you provide a smaller example demonstrating it?
It looks like Firefox treats the line feed character as a separate word for control+rightArrow, but Firefox accessibility doesn't treat the line feed as a separate word. That smells like a Firefox accessibility bug to me, though I need to dig a little further. It looks like Chrome has the same bug. Terrific.
I don't see why this is a bug. It's a different choice, yes, but there's no clear rule that line feeds should be treated as words. |
Actual: with ctrl+right arrow, in focus mode, NVDA repeats "hello", "world" and "yes" every time the carret lands on a line break. |
Just to clarify, do you have punctuation set to all? If you don't, you won't necessarily hear punctuation when moving by word. In Firefox release, control+rightArrow in Firefox doesn't stop on punctuation at the end of words. It only stops on line feeds. That is intentional. As noted above, there's definitely a bug with accessibility reporting the wrong word for line feeds though. There's an additional bug in Firefox Nightly related to punctuation; see https://bugzilla.mozilla.org/show_bug.cgi?id=1848282. That bug doesn't exist in Firefox release, though, and the related change won't ship to beta or release until this is sorted out. For now, if you're using Nightly, you can disable the problematic feature by setting intl.icu4x.segmenter.enabled to false in about:config. |
no my punctuation is set to "some", but actually the punctuation setting should not affect character and word navigation. Actually the expected behavior for punctuation setting is to affect only navigation styles greater than word navigation.
what is the reason behind this?
Thanks very much for this hint. |
Gotcha. Though I think at least in focus mode it might be worthy to find a routine that makes word navigation more consistent in edit fields in general. This does not affect only browsers, but all kinds of editors. The same problem we had for paragraphs which is now solved internally in NVDA core. |
No, this assertion is not true. There are related discussions on this topic however in #8057 #10855 and #11779 . |
That is only true if the chunk is a single character, since otherwise, you'd hear silence. For anything larger, the punctuation level applies.
This was probably modelled on the way Windows standard Edit controls work. For example, if you open the Run dialog and type there, you'll notice that control+rightArrow doesn't stop on punctuation at the end of a word there either. Unfortunately, Microsoft have been pretty inconsistent since then. Newer text boxes (not standard Edit controls) seem to implement word navigation very differently.
I disagree. The screen reader should be making as few modifications as possible to the user experience of the app. Altering that too much is asking for confusion and incompatibility. Paragraphs might have been a reasonable exception because this simply isn't supported in many controls at all. In contrast, word navigation is supported across the board. Aside from anything else, trying to enforce consistent word navigation is likely to cause a pretty severe performance hit, especially for something like word navigation where one may want to move very fast. |
Reported by camlorn on 2013-04-15 15:15
In Firefox 20.0.1 and NVDA main-5986:
When editing in edit fields, NVDA is sometimes deciding that lines are to be duplicated. Specifically, it will sometimes read the previous line again instead of the next line. If there is a post with four lines, it may sometimes read line 1 twice followed by line 3 twice, skipping 2 and 4 entirely. This is consistent, that is, it will always misread and skip the same lines, and when it starts it will always do it in pairs. It will also sometimes decide that, when moving by word, the first word of a line is the last word of the previous line, and seems to do so at the same times.
I've observed this very rarely in the NVDA ticket submission edit field. It's common on audiogames.net forums and mudconnect.com forums, shows up on topmudsites.com forums, just to name a few, but can happen in any multiline edit field. Moving by character seems to be unaffected, and selecting the text will report the correct lines and words.
This seems to be becoming more common for me. Just as an additional piece of information, jaws 13 does this as well (it may be fixed in jaws; I've not used jaws for any significant period of time for about 2 months now).
The text was updated successfully, but these errors were encountered: