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

when a table is copied from excel into word, NVDA fails to detect when you enter a table. #5927

Closed
derekriemer opened this issue May 6, 2016 · 4 comments
Assignees
Labels
Milestone

Comments

@derekriemer
Copy link
Collaborator

@derekriemer derekriemer commented May 6, 2016

This package has an excel with two sheets, and a word doc with one already pasted in.

  1. Write a bunch of text into a word doc.
  2. Paste one of the excel tables into a word doc.
  3. do the same and paste the other table in.
  4. create a new table using word.
  5. fill it in with junk.
  6. switch to browse mode.
  7. go to the top and read.
  8. Once you're in a table with data from Excel, NVDA doesn't say anything. Use table nav, it works as expected.
  9. Find the native table. Notice that all is fine.
@derekriemer
Copy link
Collaborator Author

@derekriemer derekriemer commented May 6, 2016

Loading

@derekriemer
Copy link
Collaborator Author

@derekriemer derekriemer commented May 6, 2016

Note that both of these bugs I reported with this document were discovered with real data from a biology lab, and aren't just me trying to exercise NVDA's capabilities.

Loading

@jcsteh
Copy link
Contributor

@jcsteh jcsteh commented May 25, 2016

This is because it gets treated as a layout table. A layout table is currently defined as a table with no borders, and I guess this must be true for Excel tables. This was implemented to prevent spurious announcement of layout tables in Outlook emails.

Any thoughts on how we can restrict this further, @michaelDCurran?

Loading

@michaelDCurran
Copy link
Member

@michaelDCurran michaelDCurran commented May 25, 2016

First thing that comes to mind is to restrict this specifically to Outlook browsemode. Shouldn't be too hard. Other than that we'd need to come up with a better heuristic for layout tables.

Loading

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

Successfully merging a pull request may close this issue.

None yet
4 participants