Reported by vtsaran on 2009-11-08 00:43
When using up and down arrows to read the current line inside multi-line edit fields, NVDA produces an error ding (if using snapshots) or no speech output (when using official versions).
Some examples are:
Comment 1 by vtsaran on 2009-11-08 00:48
Milestone changed from None to 2009.1
Comment 2 by pvagner on 2009-11-08 07:52
I can reproduce it with the following output in the nvda.log:
ERROR - scriptHandler.executeScript (08:48:19):
error executing script: > with key (None, 'extendedup')
Traceback (most recent call last):
File "scriptHandler.py", line 100, in executeScript
File "NVDAObjects__init__.py", line 657, in script_moveByLine
File "NVDAObjects\IAccessible\MSHTML.py", line 180, in expand
File "NVDAObjects\IAccessible\MSHTML.py", line 114, in _expandToLine
File "C:\Python26\lib\site-packages\comtypes\client\lazybind.py", line 160, in caller
return self._comobj._invoke(descr.memid, descr.invkind, 0, *args)
File "C:\Python26\lib\site-packages\comtypes\automation.py", line 649, in _invoke
dp, var, None, argerr)
COMError: (-2147467259, 'Unknown error', (None, None, None, 0, None))
Comment 3 by aleksey_s on 2009-11-11 18:33
I can't reproduce this on windows XP with IE8 and manually created page with textarea in it.
NVDA reads the text field correctly all the time.
Tested with 2009.1rc1 and the main branch
Comment 4 by jteh on 2009-11-11 22:06
Unfortunately, it seems that this bug only occurs on some multiline edit fields, not all. Mick did mention to me that he was able to reproduce it using Vic's examples, however. We suspect this might relate to the multiline edit field being floated using CSS. Unfortunately, all attempts to fix this so far have failed, so we may have ot defer to a later release.
Changed title from "IE8: NVDA does not read the current line in multi-line edit fields when arrowing up and down" to "IE8: NVDA does not read the current line in some multi-line edit fields when arrowing up and down"
Comment 5 by jteh on 2009-11-16 02:00
We are not going to be able to fix this for 2009.1.
Milestone changed from 2009.1 to 2009.2
Comment 6 by jteh on 2010-01-19 03:31
Not likely to find a fix before the release.
Milestone changed from 2010.1 to 2010.2
Comment 7 by mdcurran on 2010-07-21 06:15
Fixed in 80ce809.
If moveToPoint fails, we fall back to using the older slower and less accurate approach of moving the physical selection with key presses.