Skip to content
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

Large number of spaces in pre tag causes up arrow not to work #2812

Open
nvaccessAuto opened this issue Nov 20, 2012 · 12 comments
Open

Large number of spaces in pre tag causes up arrow not to work #2812

nvaccessAuto opened this issue Nov 20, 2012 · 12 comments

Comments

@nvaccessAuto
Copy link

Reported by tspivey on 2012-11-20 05:10
STR:

  1. Set maximum number of characters on one line to 100 in browse mode settings.
  2. Open the attached html file in either Firefox or IE - they both break.
  3. Move down to test 3, and try going back up. NVDA gets stuck, and can only go down from that point unless you use something other than the arrow keys.
  4. If I set maximum number of characters per line to something like 150, longer than that line with the extra whitespace, things work.
    I was also expecting the test 2 to all be on one line, but NVDA must think the whitespace is part of the 2.
@nvaccessAuto
Copy link
Author

nvaccessAuto commented Nov 20, 2012

Attachment test.htm added by tspivey on 2012-11-20 05:10
Description:
Update:
File added from Trac
test.htm.txt

@josephsl
Copy link
Collaborator

Hi,

Coming back to this ticket...

Any updates with 2017.2? Thanks.

@bhavyashah
Copy link

This is a friendly reminder for @tspivy to kindly respond to @josephsl's #2812 (comment) by providing a status update for this issue with the latest versions of NVDA and relevant web browsers.

@tspivey
Copy link
Collaborator

tspivey commented Aug 24, 2017

This still happens in Firefox, IE and Chrome.

@Adriani90
Copy link
Collaborator

It is still reproducible in NVDA 2018.4.1.

@Adriani90
Copy link
Collaborator

This issue is still reproducible with NVDA alpha-27818,fa89f058 (2023.2.0.27818) and Firefox 110.0.1.

@Adriani90
Copy link
Collaborator

It seems the limit is at 120 characters per line set in the browse mode settings. Having a number higher than 120 makes this work as expected.

@brunoprietog
Copy link

If it is set to 120 and the line is 121 characters long, the error will still occur

@Adriani90
Copy link
Collaborator

but not if you set 121 characters per line in browse mode settings of NVDA.

@brunoprietog
Copy link

Exactly. But the limit means that a maximum of x characters per line must be allowed. If that amount is exceeded, it continues to the next line. That doesn't mean that NVDA should get stuck on lines that have more than x spaces.

@Adriani90
Copy link
Collaborator

@brunoprietog to be clear, my statemenet with the 120 characters is for technical reasons so people understand what is this about when working on a solution. It was not meant to say it's working properly.

@brunoprietog
Copy link

Great, so sorry for the misunderstanding

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants