Navigation Menu

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

tabindex of -1 causes grid size to be incorrectly announced #927

Closed
nvaccessAuto opened this issue Sep 21, 2010 · 10 comments
Closed

tabindex of -1 causes grid size to be incorrectly announced #927

nvaccessAuto opened this issue Sep 21, 2010 · 10 comments
Labels
app/chrome app/firefox blocked/needs-external-fix bug p5 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority

Comments

@nvaccessAuto
Copy link

Reported by kloots on 2010-09-21 18:54
I have noticed that if rows in a grid have a parent element whose tabindex attribute is set to -1, NVDA will incorrectly announce the grid as having "zero rows and zero columns" when in standard browse mode (virtual buffer is on). Seems like the presence of the tabIndex attribute shouldn't affect calculation of the grid size.

Here is a an example page:

http://public.yahoo.com/kloots/bugreports/aria-grid-tabindex.html

For reference, I was testing in Firefox 3.6.8.

@LeonarddeR
Copy link
Collaborator

Unfortunately, the report contains a dead link. Might be good to track this down and, if still reproducible, fix it in #7410?

@jcsteh
Copy link
Contributor

jcsteh commented Jul 17, 2017

Still a bug which manifests in different ways in both Firefox and Chrome:

data:text/html,before<div role="grid" aria-readonly="true"><div tabindex="-1" role="presentation"><div role="row"><div role="gridcell">cell content</div></div></div></div>

Firefox incorrectly reports the row and column counts as reported here.

Chrome doesn't render the cell at all.

Bugs need to be filed with both browsers.

@jcsteh jcsteh added blocked/needs-external-fix p5 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority app/chrome app/firefox labels Jul 17, 2017
@jcsteh
Copy link
Contributor

jcsteh commented Jul 17, 2017

P4 because we don't seem to be getting reports of this particular usage in the wild. If we see a specific case of this, we can raise the priority for filing browser bugs.

@Adriani90
Copy link
Collaborator

In Firefox 66.0.3 and NVDA 2019.1.1 this issue is still reproducible. I see this issue at work very often in SAP net viewer applications.

Following error is written to the log when trying to navigate in the table cell with ctrl+alt+arrow keys:

ERROR - scriptHandler.executeScript (17:41:56.723):
error executing script: <bound method Gecko_ia2.script_previousColumn of <virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x054A40F0>> with gesture u'Alt+Strg+Pfeiltaste nach links'
Traceback (most recent call last):
  File "scriptHandler.pyc", line 187, in executeScript
  File "documentBase.pyc", line 189, in script_previousColumn
  File "documentBase.pyc", line 167, in _tableMovementScriptHelper
  File "virtualBuffers\gecko_ia2.pyc", line 337, in _getTableCellAt
LookupError

@Adriani90
Copy link
Collaborator

In Chrome 74 it works as expected. The text "cell content" is rendered into a cell and you can navigate by ctrl+alt+arrow keys.

@Adriani90
Copy link
Collaborator

I get this behavior also in many share point applications which contain grids.

@Adriani90
Copy link
Collaborator

Still reproducible in Firefox 71. @jcsteh is this something you could report on Bugzilla? Unfortunately this issue is quite severe in corporate environments, epsecially in sharepoint based interfaces and the table navigation does not work.

@jcsteh
Copy link
Contributor

jcsteh commented Dec 15, 2019

@jcsteh
Copy link
Contributor

jcsteh commented Mar 13, 2020

This should be addressed in Firefox 75 (currently in beta). The simple test case in #927 (comment) now works as expected.

@Adriani90, could you test whether the problematic SAP net viewer and SharePoint applications you mentioned are fixed now? I understand you may not be able to run beta software in a corporate environment, so we might have to wait until Firefox 75 final.

@jcsteh
Copy link
Contributor

jcsteh commented Mar 13, 2020

I'm closing this, since the test case is fixed, but please do comment with your findings. We should open a new issue if there are further problems.

@jcsteh jcsteh closed this as completed Mar 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app/chrome app/firefox blocked/needs-external-fix bug p5 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Development

No branches or pull requests

4 participants