https://bugs.documentfoundation.org/show_bug.cgi?id=167090

--- Comment #3 from ady <[email protected]> ---
The problem is how exactly you define each action.

Currently:
_ [ALT]+[left_arrow]: "shrink" column width
_ [ALT]+[right_arrow]: "enlarge" column width

and both:
_[ALT]+[SHIFT]+[left_arrow]
_[ALT]+[SHIFT]+[right_arrow]

become "adjust the column to optimal width depending on selected range".

So the current actions are not inconsistent, because they are not dependent on
language, worksheet direction, or UI language.

Moreover, there is also the Cursor Control Movement (Logical vs Visual), which
is kind of a "fight" by itself among users.

Considering that a user could have in the same workbook some worksheets that
are LTR, other worksheets that are RTL, (and even multiple languages in the
same cell), then any change of the current logic will make things more
inconsistent. Just imagine a user with a combination of those cases having to
permanently pay attention to whether the specific spreadsheet is set to LTR or
RTL before intuitively using the "adequate" keyboard shortcut according to any
number of settings – even one conditional branch would only complicate the
usage of keyboard shortcuts.

A keyboard shortcut is useful when the user incorporates it as a natural
reflect (e.g. [ALT]+[left_arrow] means "shrink" column width, no matter what).
If the user has to ponder additional considerations before using the keyboard
shortcut each and every time, then the shortcuts will not be used.

Changing the behavior will only mess things for most scenarios. The only group
of users that _might_ perhaps benefit from adding conditions to these keyboard
shortcuts could be those that _always_ use one exclusive language direction on
one exclusive worksheet direction. Any other combination (which is by far the
most common) will not benefit from the proposed change.

The description of the shortcuts might need some improvement / precise
definition, but modifying the current behavior will not be beneficial.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to