Ticket #1831 (closed defect: fixed)

Opened 7 months ago

Last modified 7 months ago

Regression: System menu in IE8 in xP no longer works with alt/space

Reported by: briang1 Owned by:
Priority: minor Milestone: 2011.3
Component: Core Version: 2011.3beta1
Keywords: regression Cc:
Operating system: Windows XP Blocked by:
Blocking:

Description

When trying to access the system menu in IE 8 in Windows XP it can only be accessed by Object navigation and o launched with mouse clicks. Using alt/space simply results in no apparent action.

Testing the snaps I have to find out when this went wrong shows that [main,4592] works and...
main,4603 does not work. Though there is no obvious smoking gun in that gap.

The log of the non working versions looks like..

IO - inputCore.InputManager?.executeGesture (19:44:30):
Input: kb(desktop):alt+space
DEBUGWARNING - watchdog._watcher (19:44:30):
Trying to recover from freeze, core stack:

File "nvda.pyw", line 156, in <module>
File "core.pyc", line 301, in main
File "wx\_core.pyc", line 8007, in MainLoop?
File "wx\_core.pyc", line 7303, in MainLoop?
File "core.pyc", line 287, in Notify
File "queueHandler.pyc", line 76, in pumpAll
File "queueHandler.pyc", line 47, in flushQueue
File "eventHandler.pyc", line 54, in _queueEventCallback
File "eventHandler.pyc", line 131, in executeEvent
File "eventHandler.pyc", line 144, in doPreGainFocus
File "api.pyc", line 113, in setFocusObject
File "treeInterceptorHandler.pyc", line 43, in cleanup
File "baseObject.pyc", line 21, in get
File "virtualBuffers\MSHTML.pyc", line 187, in _get_isAlive
File "baseObject.pyc", line 34, in get
File "baseObject.pyc", line 110, in _getPropertyViaCache
File "NVDAObjects\IAccessible\init.pyc", line 738, in

_get_IAccessibleRole

File "comtypes\init.pyc", line 795, in call

DEBUGWARNING - eventHandler.executeEvent (19:44:30):
error executing event: gainFocus on <NVDAObjects.IAccessible.MenuItem? object
at 0x021A5B30> with extra args of {}
Traceback (most recent call last):

File "eventHandler.pyc", line 131, in executeEvent
File "eventHandler.pyc", line 144, in doPreGainFocus
File "api.pyc", line 113, in setFocusObject
File "treeInterceptorHandler.pyc", line 43, in cleanup
File "baseObject.pyc", line 21, in get
File "virtualBuffers\MSHTML.pyc", line 187, in _get_isAlive
File "baseObject.pyc", line 34, in get
File "baseObject.pyc", line 110, in _getPropertyViaCache
File "watchdog.pyc", line 147, in _COMError_init

CallCancelled?
DEBUGWARNING - watchdog._watcher (19:44:30):
Trying to recover from freeze, core stack:

File "nvda.pyw", line 156, in <module>
File "core.pyc", line 301, in main
File "wx\_core.pyc", line 8007, in MainLoop?
File "wx\_core.pyc", line 7303, in MainLoop?
File "core.pyc", line 287, in Notify
File "queueHandler.pyc", line 76, in pumpAll
File "queueHandler.pyc", line 47, in flushQueue
File "eventHandler.pyc", line 54, in _queueEventCallback
File "eventHandler.pyc", line 131, in executeEvent
File "eventHandler.pyc", line 144, in doPreGainFocus
File "api.pyc", line 113, in setFocusObject
File "treeInterceptorHandler.pyc", line 43, in cleanup
File "baseObject.pyc", line 21, in get
File "virtualBuffers\MSHTML.pyc", line 187, in _get_isAlive
File "baseObject.pyc", line 34, in get
File "baseObject.pyc", line 110, in _getPropertyViaCache
File "NVDAObjects\IAccessible\init.pyc", line 738, in

_get_IAccessibleRole

File "comtypes\init.pyc", line 795, in call

DEBUGWARNING - eventHandler.executeEvent (19:44:30):
error executing event: gainFocus on <NVDAObjects.IAccessible.MenuItem? object
at 0x020EF510> with extra args of {}
Traceback (most recent call last):

File "eventHandler.pyc", line 131, in executeEvent
File "eventHandler.pyc", line 144, in doPreGainFocus
File "api.pyc", line 113, in setFocusObject
File "treeInterceptorHandler.pyc", line 43, in cleanup
File "baseObject.pyc", line 21, in get
File "virtualBuffers\MSHTML.pyc", line 187, in _get_isAlive
File "baseObject.pyc", line 34, in get
File "baseObject.pyc", line 110, in _getPropertyViaCache
File "watchdog.pyc", line 147, in _COMError_init

CallCancelled?

Change History

comment:1 Changed 7 months ago by briang1

The nvda/f1 output looks like this.

INFO - globalCommands.GlobalCommands?.script_navigatorObject_devInfo (13:52:56):
Developer info for navigator object:
name: exception:
role: exception:
states: exception:
Python object: <NVDAObjects.Dynamic_EditableTextWithoutAutoSelectDetectionBodyMSHTMLIAccessibleWindowNVDAObject object at 0x01DEDDD0>
Python class mro: (<class 'NVDAObjects.Dynamic_EditableTextWithoutAutoSelectDetectionBodyMSHTMLIAccessibleWindowNVDAObject'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection?'>, <class 'editableText.EditableTextWithoutAutoSelectDetection?'>, <class 'NVDAObjects.behaviors.EditableText?'>, <class 'editableText.EditableText?'>, <class 'NVDAObjects.IAccessible.MSHTML.Body'>, <class 'NVDAObjects.IAccessible.MSHTML.MSHTML'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject?'>, <class 'baseObject.AutoPropertyObject?'>, <type 'object'>)
description: exception:
location: exception:
value: exception:
appModule: <'appModuleHandler' (appName u'iexplore', process ID 3444) at address 1ded8d0>
TextInfo?: <class 'NVDAObjects.IAccessible.MSHTML.MSHTMLTextInfo'>
windowHandle: 66650
windowClassName: u'Internet Explorer_Server'
windowControlID: 0
windowStyle: 1442840576
windowThreadID: 2676
windowText: u
IAccessibleObject: <POINTER(IAccessible) ptr=0x1b6d48 at 1e0d4e0>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=66650, objectID=-4, childID=0
IAccessible accRole: exception:
IAccessible accState: exception:

comment:2 Changed 7 months ago by jteh

  • Keywords regression added
  • Status changed from new to closed
  • Version changed from development to 2011.3beta1
  • Resolution set to fixed
  • Milestone set to 2011.3

This damned problem again. I am seriously sick of this XP IE 8 system menu. :(

Regression probably caused by changeset:main,4628. Not sure why you're seeing this in 4603, but I can't see any reason it should occur there.

In any case, it's fixed for me by changeset:main,4736.

comment:3 Changed 7 months ago by briang1

I was alerted to this by someone who did not want to do a ticket. He too noticed it in the same snap, I went back to 92 and it was OK but not in 603, soI don't know. I'll test it later on and report.
It is an odd one.

comment:4 Changed 7 months ago by briang1

Yes its working again. The usual delay of course.

Thanks

Note: See TracTickets for help on using tickets.