On some web sites, Internet Explorer 8 seems to induce an error on nvda on going into an edit field with auto focus mode on. Try this site and cursor down to the ask a question field.
My log looks like this.
Speaking ('en_UK'), u'blank'
IO - inputCore.InputManager.executeGesture (16:01:37):
Input: kb(desktop):downArrow
IO - speech.speak (16:01:37):
Speaking ('en_UK'), u'blank'
IO - inputCore.InputManager.executeGesture (16:01:38):
Input: kb(desktop):downArrow
IO - speech.speak (16:01:38):
Speaking ('en_UK'), u'edit clickable', u'Ask a software-related question. You will get a free expert answer.', u'button', u' '
IO - speech.speak (16:01:38):
Speaking ('en_UK'), u'focus mode'
ERROR - eventHandler.executeEvent (16:01:38):
error executing event: focusEntered on <NVDAObjects.IAccessible.MSHTML.MSHTML object at 0x03DB1890> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 136, in executeEvent
File "eventHandler.pyc", line 84, in init
File "eventHandler.pyc", line 91, in next
File "virtualBuffers__init__.pyc", line 1018, in event_focusEntered
File "eventHandler.pyc", line 91, in next
File "NVDAObjects__init__.pyc", line 767, in event_focusEntered
File "speech.pyc", line 300, in speakObject
File "speech.pyc", line 265, in speakObjectProperties
File "speech.pyc", line 840, in getSpeechTextForProperties
TypeError: sequence item 0: expected string, Dispatch found
IO - speech.speak (16:01:38):
Speaking ('en_UK'), u'edit'
IO - speech.speak (16:01:38):
Speaking ('en_UK'), u'blank'
IO - inputCore.InputManager.executeGesture (16:01:47):
Input: kb(desktop):control+alt+r
INFO - core.main (16:01:48):
Exiting
This seems only to happen in IE Firefox seems to be OK.
The text was updated successfully, but these errors were encountered:
Comment 1 by jteh on 2012-02-23 04:29
On this site, retrieving the title attribute on the form returns an input node. I have no idea why, but it doesn't make any sense and I'm pretty sure it shouldn't happen. I've worked around it in aa5cf1f.
Changes:
Milestone changed from None to 2012.1
State: closed
Comment 2 by briang1 on 2012-02-23 10:26
There were a couple of other sites like this, both web based forums, so it might well be they are using the same code.
Unfortunately, I nevr logged the addresses!
Reported by briang1 on 2012-02-22 16:14
On some web sites, Internet Explorer 8 seems to induce an error on nvda on going into an edit field with auto focus mode on. Try this site and cursor down to the ask a question field.
http://software-informer.software.informer.com/
My log looks like this.
Speaking ('en_UK'), u'blank'
IO - inputCore.InputManager.executeGesture (16:01:37):
Input: kb(desktop):downArrow
IO - speech.speak (16:01:37):
Speaking ('en_UK'), u'blank'
IO - inputCore.InputManager.executeGesture (16:01:38):
Input: kb(desktop):downArrow
IO - speech.speak (16:01:38):
Speaking ('en_UK'), u'edit clickable', u'Ask a software-related question. You will get a free expert answer.', u'button', u' '
IO - speech.speak (16:01:38):
Speaking ('en_UK'), u'focus mode'
ERROR - eventHandler.executeEvent (16:01:38):
error executing event: focusEntered on <NVDAObjects.IAccessible.MSHTML.MSHTML object at 0x03DB1890> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 136, in executeEvent
File "eventHandler.pyc", line 84, in init
File "eventHandler.pyc", line 91, in next
File "virtualBuffers__init__.pyc", line 1018, in event_focusEntered
File "eventHandler.pyc", line 91, in next
File "NVDAObjects__init__.pyc", line 767, in event_focusEntered
File "speech.pyc", line 300, in speakObject
File "speech.pyc", line 265, in speakObjectProperties
File "speech.pyc", line 840, in getSpeechTextForProperties
TypeError: sequence item 0: expected string, Dispatch found
IO - speech.speak (16:01:38):
Speaking ('en_UK'), u'edit'
IO - speech.speak (16:01:38):
Speaking ('en_UK'), u'blank'
IO - inputCore.InputManager.executeGesture (16:01:47):
Input: kb(desktop):control+alt+r
INFO - core.main (16:01:48):
Exiting
This seems only to happen in IE Firefox seems to be OK.
The text was updated successfully, but these errors were encountered: