Issue 23952 - need kind of "tabstop" property for grid columns, to exclude them from keyboard navigation
Summary: need kind of "tabstop" property for grid columns, to exclude them from keyboa...
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC5
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2003-12-29 19:36 UTC by amoroder2
Modified: 2017-05-20 10:44 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description amoroder2 2003-12-29 19:36:01 UTC

Creating a form with a table grid, if one field ( column ) is set to active=No
pressing the tabulator this field continues to be in the tabstop list.

I try to explain with a example:
table grid with 3 colums
Column 1 and 3 are active=yes
column 2 active=no
Set the focus to column 1
You must now press TAB two times to go to the column 3. Only one should be
necessary because the second field ( column ) is not active.
The seems also to be a problem with read-only ( nur lesen ) for columns. Even if
set I can change the values in the field.

Comment 1 marc.neumann 2004-01-05 08:22:34 UTC

I can reproduce this. set target and send to the right developer.

Bye Marc
Comment 2 Frank Schönheit 2004-01-05 08:54:06 UTC
This cannot be fixed - you need to be able to completely operate the control
with the keyboard, this is simply an accessibility requirement. This also
includes that you must be able to, e.g., copy the content of the cell to the
clipboard with only using they keyboard. If we would remove the column from the
tabbing order, this would not be possible anymore. So this is a WONTFIX (well, a
CANTFIX, if we would have this :).
We can argue that the current cell is not distinguishable in case it's not
activated, which is another accessibility problem.

For the readonly problem you mention in passing by, please submit another issue
describing your problem in more detail - at the moment, I do not know what you mean.
Comment 3 Frank Schönheit 2004-01-05 08:54:22 UTC
Comment 4 amoroder2 2004-01-09 15:57:33 UTC
Hello Frank,

I don't agree. This is not the way standard controls work. If you set active=no
in a standard control it is completely disabled ( no way to select the text
inside, no way to set the focus inside ). Why should this be different in the
grid control ?
If I want a field to be protected from writing, I use readonly=yes  ( Nur Lesen
)  combined with enabled=no ( with standard controls )

Comment 5 Frank Schönheit 2004-01-09 16:09:26 UTC
Okay, I accept this because of the inconsistency, and because I see the need to
exclude a column from keyboard navigation. However, I don't think that this
should (and can) be targeted for 2.0 then.

Changing summary from
  "Disabled field in data grid remains in tabstop order"
  "need kind of "tabstop" property for grid columns, to exclude them from
   keyboard navigation"

Comment 6 amoroder2 2004-01-10 07:12:39 UTC

it would be nice to have a tabstop propertie in the grid.
Sorry if I nerve-racking, but this tabstop would not change the inconsistency.
If enabled=no and read onyl=no then the field ( column ) must be "unselectable".
Even with the mouse it is impossible to set the focus on normal fields that have
this two properties set, this should be the same in the grid.

Comment 7 hans_werner67 2004-02-02 12:12:22 UTC
change subcomponent to 'none'
Comment 8 Frank Schönheit 2005-07-25 13:38:37 UTC
Comment 9 Marcus 2017-05-20 10:44:12 UTC
Reset the assignee to the default "".