Report table row/column headers in IE #778

Closed
nvaccessAuto opened this Issue Jul 22, 2010 · 9 comments

2 participants

@nvaccessAuto

Reported by briang1 on 2010-07-22 15:46
Well, not much else to say, but in many instances, there is little one can remember the relative locations in tables with, other than the numbers.
Its always been my dream to have a kind of dual focus toggle so I can actually be sure which box I'm ticking in table based forms etc.

@nvaccessAuto

Comment 1 by jteh on 2010-09-23 02:22
This should be covered by #361, although that only works in Mozilla applications for now. If that is acceptable, we should close this as a duplicate. Otherwise, this ticket should be morphed to cover table headers in IE.

@nvaccessAuto

Comment 2 by briang1 on 2010-09-23 08:05
OK, obviously not had time to eveluate the effects in FF as yet, but yes, I kept it unspecific on browser as I wanted it in the two main ones. I'll add something to the short description.
I'm not sure if its a duplicate, I do try to search for common words etc before I raise one, but sometimes the words might be wrong!
Changes:
Changed title from "Feature request. Be able to read column heading without moving current focus in large tables" to "Feature request. In IE/Firefox, Be able to read column heading without moving current focus in large tables"

@nvaccessAuto

Comment 3 by jteh on 2010-11-26 01:07
Changes:
Changed title from "Feature request. In IE/Firefox, Be able to read column heading without moving current focus in large tables" to "Report table row/column headers in IE"

@nvaccessAuto

Comment 4 by mdcurran on 2010-12-01 06:59
Changes:
Milestone changed from 2011.1 to near-term

@nvaccessAuto

Comment 5 by jteh on 2012-08-11 11:55
Changes:
Milestone changed from near-term to None

@nvaccessAuto

Comment 6 by mdcurran on 2012-11-05 11:22
Initial implementation in eb5888f. Much code borrowed from adobeAcrobat backend.
Remaining problems: breakage if table is mutated. Guessing could be better when no scope is provided.
Changes:
Milestone changed from None to 2013.1

@nvaccessAuto

Comment 7 by mdcurran on 2012-11-06 07:52
Table mutation breakage now fixed in b4e60a3.
Ignoring the scope issue for this ticket. If there are any basic tables found that suggest a better handling of undefined scope, a new ticket should be opened.
Changes:
State: closed

@nvaccessAuto

Comment 8 by jteh on 2012-11-27 23:40
This needs a What's New entry.

@nvaccessAuto

Comment 9 by briang1 on 2012-11-28 17:36
[NVDA] #2824: Incorrect column headers in IE 8 on ticket system for nvda was raised a couple of days ago. If you go to the top of a ticket and come down the table you encounter first you can see what I am getting at in the ticket, and Firefox seems to cope properly.

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