Issue 102317

Summary: Custom properties: deleting a property with the keyboard sets the focus nowhere
Product: General Reporter: eric.savary
Component: uiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P4 CC: h.ilter, issues
Version: OOo 3.1   
Target Milestone: ---   
Hardware: Unknown   
OS: Windows Vista   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description eric.savary 2009-05-27 23:45:38 UTC
Preamble: I set P4/3.3 because it is not that dramatic but it is obvious that it
may have bad influence on ACCESSIBILITY....

- New document
- File - Properties - Custom Properties
- Add 2 properties
(the cursor is now in the first field of the second property)
- travel with Tab to the "Delete" button
- press Space to delete
-> where is the focus?
- press Space again
-> a "ghost" Delete-button appears where the deleted row used to be -> bug

Expected (can be discussed):
1. CASE the deleted row was the last one in the list (but there are others above
him)
-> the focus gets to the Delete-button of the now last row.
Example:
row1
row2
row3

- row3 deleted
-> focus jumps on Row2 Delete-button to allow:
a) a clean focus on an existing control
b) a quick deletion of all the rows pressing Space, Space, Space...

2. CASE the deleted row has other rows beneath him
-> the focus gets to the Delete-button of the next row.
Example:
row1
row2
row3

- row1 deleted
-> focus jumps on Row2 Delete-button to allow:
See a) and b) above

3. CASE the deleted row was the only one in the list
-> the focus gets to the Ok button of the dialog

[I just assume here the user wanted to delete every properties and leave.
One may also set the focus on the Add button]

-> focus jumps on Ok Delete-button to allow:
- See a) above
- a quick leave of the dialog
Comment 1 pb 2010-06-08 12:56:42 UTC
@cd: please take over. Thanks.
Comment 2 carsten.driesner 2010-06-25 07:48:41 UTC
cd: Move to OOo 3.4.
Comment 3 Martin Hollmichel 2011-03-15 21:00:41 UTC
set target to 3.x since not release relevant for 3.4 release.