Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error in google docs table nav #9494

derekriemer opened this issue Apr 15, 2019 · 2 comments

error in google docs table nav #9494

derekriemer opened this issue Apr 15, 2019 · 2 comments


Copy link

@derekriemer derekriemer commented Apr 15, 2019

Steps to reproduce:

  1. open a new docs document with braille mode enabled.
  2. create a 3x3 table.
  3. fill out the table.
  4. try to press alt+ctrl+<arrow keys>

Actual behavior:

Input: kb(laptop):alt+control+downArrow
ERROR - scriptHandler.executeScript (12:43:20.176):
error executing script: <bound method Dynamic_EditableTextWithAutoSelectDetectionEditorIa2WebIAccessible.script_nextRow of <NVDAObjects.Dynamic_EditableTextWithAutoSelectDetectionEditorIa2WebIAccessible object at 0x0380B150>> with gesture u'alt+ctrl+down arrow'
Traceback (most recent call last):
  File "scriptHandler.pyc", line 187, in executeScript
  File "documentBase.pyc", line 174, in script_nextRow
  File "documentBase.pyc", line 161, in _tableMovementScriptHelper
  File "documentBase.pyc", line 126, in _getNearestTableCell
TypeError: coercing to Unicode: need string or buffer, int found

Expected behavior:

NVDA can move around the table.

System configuration

NVDA installed/portable/running from source:


NVDA version:


Windows version:


Name and version of other software in use when reproducing the issue:

docs, chrome, firefox

Other information about your system:

Other questions

Have you tried any other versions of NVDA? If so, please report their behaviors.

worked before 2019.1

Copy link

@DrSooom DrSooom commented Apr 15, 2019

@derekriemer: Please add the Chrome and Firefox version to the issue description and try with NVDA 2019.1.1 as well. Thanks.


Copy link
Collaborator Author

@derekriemer derekriemer commented Apr 19, 2019

happens with 2019.1.1 and it's an NVDA bug it seems. No need to add firefox and chrome versions, it occurs with them all after 2019.1.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants