Steps to reproduce:
- Load a page with at least somewhat accessible Flash Content in Internet Explorer or the new Microsoft Edge.
- Press enter on the flash object.
Actual behavior:
In Internet Explorer, chosen because it tends to support Flash by default, the only thing that happens is that the name of the object gets spoken after "embedded object". No focus change, the content of the object remains unreachable. In the logs, nothing at all is reported when pressing enter or loading the relevant page, not even in Debug mode.
In Edge based on Chrome, the embedded object reports as being "unavailable", and this, possibly relevant, log output shows up. Note: This might also be happening because of me navigating to the permissions popup to allow flash.
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (13:55:26.198) - MainThread (5608):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (13:55:26.659) - MainThread (5608):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None))
IO - speech.speak (13:55:26.669) - MainThread (5608):
Speaking [LangChangeCommand ('en'), 'Laden voltooid']
IO - braille.BrailleBuffer.update (13:55:26.670) - MainThread (5608):
Braille regions text: ['Laden voltooid']
IO - braille.BrailleHandler.update (13:55:26.670) - MainThread (5608):
Braille window dots: 6 123 1 145 15 1345 - 1236 135 123 2345 135 135 24 145
IO - inputCore.InputManager.executeGesture (13:55:28.397) - winInputHook (8388):
Input: kb(laptop):f6
DEBUG - treeInterceptorHandler.killTreeInterceptor (13:55:28.428) - MainThread (5608):
Killed treeInterceptor: <NVDAObjects.IAccessible.chromium.ChromeVBuf object at 0x07209630>
DEBUG - treeInterceptorHandler.update (13:55:28.446) - MainThread (5608):
Adding new treeInterceptor to runningTable: <NVDAObjects.IAccessible.chromium.ChromeVBuf object at 0x07277B90>
DEBUG - virtualBuffers.VirtualBuffer._loadBuffer (13:55:28.447) - NVDAObjects.IAccessible.chromium.VirtualBuffer.loadBuffer (18740):
Buffer load took 0.001 sec, 1 chars
DEBUGWARNING - RPC process 22284 (msedge.exe) (13:55:28.471) - Dummy-5 (152):
Thread 14452, build\x86_64\vbufBase\storage.cpp, VBufStorage_buffer_t::findNodeByAttributes, 967:
offset 1 is past end of buffer, returning NULL
DEBUGWARNING - RPC process 22284 (msedge.exe) (13:55:28.478) - Dummy-5 (152):
Thread 14452, build\x86_64\vbufBase\storage.cpp, VBufStorage_buffer_t::locateTextFieldNodeAtOffset, 859:
Offset 1 out of range. Returnning NULL
DEBUGWARNING - RPC process 22284 (msedge.exe) (13:55:28.487) - Dummy-5 (152):
Thread 14452, build\x86_64\vbufBase\storage.cpp, VBufStorage_buffer_t::locateControlFieldNodeAtOffset, 879:
Could not locate node at offset, returning NULL
DEBUGWARNING - virtualBuffers.VirtualBufferTextInfo._getNVDAObjectFromOffset (13:55:28.487) - MainThread (5608):
Couldn't get NVDAObject from offset 1
DEBUGWARNING - browseMode.BrowseModeDocumentTreeInterceptor._set_selection (13:55:28.487) - MainThread (5608):
Invalid NVDAObjectAtStart
IO - speech.speak (13:55:28.488) - MainThread (5608):
Speaking [LangChangeCommand ('en'), 'Game Page']
IO - speech.speak (13:55:28.489) - MainThread (5608):
Speaking [<speech.commands.CallbackCommand object at 0x005EB330>]
DEBUGWARNING - RPC process 22284 (msedge.exe) (13:55:28.498) - Dummy-5 (152):
Thread 14452, build\x86_64\vbufBase\storage.cpp, VBufStorage_buffer_t::getLineOffsets, 1055:
Offset of 1 too big for buffer, returning false
Expected behavior:
The contents of the flash object should be readable.
System configuration
NVDA installed/portable/running from source: 2019.3.1, installed
Windows version: 1903
Name and version of other software in use when reproducing the issue: Internet Explorer latest, MS Edge v81.0
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If addons are disabled, is your problem still occuring?
Yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
No
Steps to reproduce:
Actual behavior:
In Internet Explorer, chosen because it tends to support Flash by default, the only thing that happens is that the name of the object gets spoken after "embedded object". No focus change, the content of the object remains unreachable. In the logs, nothing at all is reported when pressing enter or loading the relevant page, not even in Debug mode.
In Edge based on Chrome, the embedded object reports as being "unavailable", and this, possibly relevant, log output shows up. Note: This might also be happening because of me navigating to the permissions popup to allow flash.
Expected behavior:
The contents of the flash object should be readable.
System configuration
NVDA installed/portable/running from source: 2019.3.1, installed
Windows version: 1903
Name and version of other software in use when reproducing the issue: Internet Explorer latest, MS Edge v81.0
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If addons are disabled, is your problem still occuring?
Yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
No