Allow TextInfos and NVDAObjects to provide specific location information when pressing reportCurrentDimensions script (NVDA+numpadDelete). #4219

nvaccessAuto opened this Issue Jun 24, 2014 · 5 comments

1 participant


Reported by mdcurran on 2014-06-24 05:00
E.g. cursor distance from page left edge in MS Word, Shape distance from slide edges in MS Powerpoint, Percentage through web document.
Blocking #1487


Comment 2 by Michael Curran <mick@... on 2014-06-24 05:30
In [a998275]:
```CommitTicketReference repository="" revision="a998275c4ba5ac1bf7bb5c0c747f99c4db2ca84e"
Merge branch 't4219' into next. Incubates #4219

Added labels: incubating

Comment 3 by Michael Curran <mick@... on 2014-07-07 09:05
In [2f64906]:
```CommitTicketReference repository="" revision="2f64906d6587bd3a68fcd924e9006deec76235e5"
Merge branch 't4219'. Fixes #4219

Removed labels: incubating
State: closed

Comment 4 by mdcurran on 2014-07-07 09:06
Milestone changed from next to 2014.3


Comment 6 by tspivey on 2014-08-05 04:32
I think it would be useful to have a space after the comma in the coordinates. Compare 120,708 and 120, 708. The second makes it obvious that it's two numbers, and not a number in the thousands.

In some edit controls (e.g. notepad), but not others (notepad2 or firefox), and for small amounts of text (a few words or so), the percentage is off by a bit -- the end of the document isn't 100%. It's easiest to see this by typing one letter.


Comment 7 by Michael Curran <mick@... on 2014-08-05 05:03
In [6c0a602]:
```CommitTicketReference repository="" revision="6c0a6025bb71cd6cb6b74570c2bdabab302bbf8d"
report current dimensions script: separate pixel coordinates by a comma and a space, rather than just a comma so as to make it not look simply like one number in the thousands. re #4219

@nvaccessAuto nvaccessAuto added this to the 2014.3 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment