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

strip space between table coordinates #7453

Open
gregjozk opened this issue Jul 28, 2017 · 3 comments
Open

strip space between table coordinates #7453

gregjozk opened this issue Jul 28, 2017 · 3 comments

Comments

@gregjozk
Copy link
Contributor

gregjozk commented Jul 28, 2017

as @LeonarddeR suggested at issue #7188 (comment) I'm opening a separate issue for the point, which was suggested first in #7450

Expected behavior:

in braille there should be reported "tb RxCy" and tb should be always presented for consistency reasons. this behaviour is also expected in a lists.

Actual behavior:

tb rx cy (tb is presented only at first column and row - tb r1 c1)
and for lists: lst (first element) other elements are unmarked with abbreviation.

System configuration:

NVDA version:
2017.2

NVDA Installed or portable:
both

Windows version:
w10 1703 with latest updates

@AAClause
Copy link
Contributor

I'm working on this issue through Braille Extender add-on. See AAClause/BrailleExtender#64

Here's some sample outputs:

  • tb(4,2): table with 4 lines and 2 columns
  • r1c3: row 1, column 3
  • r1c3(website): row 1 column 3 with "website" as header text

All these outputs will be soon customizable.
Can be tested with the development version of the add-on. Any suggestion are welcome!

@michaelDCurran
Copy link
Member

Is this issue asking to always include tb before coordinates on the display, even when not at the start of the table? If so then the title is misleading.

@Adriani90
Copy link
Collaborator

Looking at the referenced issues in the description, this one is formulated in a quite confusing way. The author actually requests to remove the space between row and column coordinates.

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

Successfully merging a pull request may close this issue.

5 participants