cursor can't read past the first line in html multiline edit fields

[vortex1024]

str:

1. open:
   https://www.w3schools.com/html/tryit.asp?filename=tryhtml_elem_textarea
2. in the second edit field, write:
   "
   we have to see
   why this is not working
   "
3. go to the second line.
4. when trying to move with ctrl+left and right arrow, no matter if we use right or left control, the cursor is tuc on the first line, reading only "we have to see" in a loop.

Google Chrome version 87.0.4280.88
NVDA version 2020.3
wordnav 1.2, windows 10
currently, the workaround I've found is to disable it in chrome.

[mltony]

This is due to underlying bug in NVDA: nvaccess/nvda#11931 Please leave your comment there to increase visibility.

…

On 1/5/2021 8:49 AM, vortex1024 wrote: str: 1. open: https://www.w3schools.com/html/tryit.asp?filename=tryhtml_elem_textarea <https://www.w3schools.com/html/tryit.asp?filename=tryhtml_elem_textarea> 2. in the second edit field, write: " we have to see why this is not working " 3. go to the second line. 4. when trying to move with ctrl+left and right arrow, no matter if we use right or left control, the cursor is tuc on the first line, reading only "we have to see" in a loop. Google Chrome version 87.0.4280.88 NVDA version 2020.3 wordnav 1.2, windows 10 currently, the workaround I've found is to disable it in chrome. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIJRDHFX7DSB35BPJ7VFPRTSYM7KDANCNFSM4VVRLS3Q>.

[vortex1024]

Got it, done. Is it ok if we leave this open, so I can be notified when it is fixed? From: mltony Sent: Tuesday, January 5, 2021 6:59 PM To: mltony/nvda-word-nav Cc: vortex1024 ; Author Subject: Re: [mltony/nvda-word-nav] cursor can't read past the first line in html multiline edit fields (#3) This is due to underlying bug in NVDA: nvaccess/nvda#11931 Please leave your comment there to increase visibility.

On 1/5/2021 8:49 AM, vortex1024 wrote: str: 1. open: https://www.w3schools.com/html/tryit.asp?filename=tryhtml_elem_textarea <https://www.w3schools.com/html/tryit.asp?filename=tryhtml_elem_textarea> 2. in the second edit field, write: " we have to see why this is not working " 3. go to the second line. 4. when trying to move with ctrl+left and right arrow, no matter if we use right or left control, the cursor is tuc on the first line, reading only "we have to see" in a loop. Google Chrome version 87.0.4280.88 NVDA version 2020.3 wordnav 1.2, windows 10 currently, the workaround I've found is to disable it in chrome. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIJRDHFX7DSB35BPJ7VFPRTSYM7KDANCNFSM4VVRLS3Q>.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[mltony]

Sure, no problem.

…

On 1/5/2021 12:46 PM, vortex1024 wrote: Got it, done. Is it ok if we leave this open, so I can be notified when it is fixed? From: mltony Sent: Tuesday, January 5, 2021 6:59 PM To: mltony/nvda-word-nav Cc: vortex1024 ; Author Subject: Re: [mltony/nvda-word-nav] cursor can't read past the first line in html multiline edit fields (#3) This is due to underlying bug in NVDA: nvaccess/nvda#11931 Please leave your comment there to increase visibility. On 1/5/2021 8:49 AM, vortex1024 wrote: > > str: > > 1. open: > https://www.w3schools.com/html/tryit.asp?filename=tryhtml_elem_textarea > <https://www.w3schools.com/html/tryit.asp?filename=tryhtml_elem_textarea> > 2. in the second edit field, write: > " > we have to see > why this is not working > " > 3. go to the second line. > 4. when trying to move with ctrl+left and right arrow, no matter if > we use right or left control, the cursor is tuc on the first line, > reading only "we have to see" in a loop. > > Google Chrome version 87.0.4280.88 > NVDA version 2020.3 > wordnav 1.2, windows 10 > currently, the workaround I've found is to disable it in chrome. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#3>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIJRDHFX7DSB35BPJ7VFPRTSYM7KDANCNFSM4VVRLS3Q>. > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIJRDHASJ4KR657EPRAAUCLSYN3CLANCNFSM4VVRLS3Q>.

[mltony]

I did some more investigation on this and managed to drill down to an underlying issue in chromium. I reported that issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=1260726

[mltony]

I think I found a workaround for this issue. Please check v1.5.

[vortex1024]

yes, it works! thanks for the fix