Page MenuHomePhabricator

If "More" menu contains only one item (usually "Move"), display the item instead of "More"
Closed, DuplicatePublic

Description

A user suggested on IRC that when the "More" menu has only the "Move" item (i.e. in most cases), this item should be displayed instead of the label.

Now that the menu occupies more space than just an icon, I think it makes sense to put the useful link directly in that spot, instead of requiring the user to click just to click again in the only option available.directly


T26481: [collapsibleTabs] Vector: Tab "Move" should be visible by default (to discourage copy/paste moves)

Details

Reference
bz68774

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 3:30 AM
bzimport set Reference to bz68774.
bzimport added a subscriber: Unknown Object (MLST).

swalling wrote:

(In reply to Helder from comment #0)

A user suggested on IRC that when the "More" menu has only the "Move" item
(i.e. in most cases), this item should be displayed instead of the label.

Now that the menu occupies more space than just an icon, I think it makes
sense to put the useful link directly in that spot, instead of requiring the
user to click just to click again in the only option available.directly

Seems like a good idea. James?

This seems good in English; for other languages, I'm not sure it works very well as "move" and "more" are not generally translated to the same length words:

Looking at our big languages:

1x
ja: その他 vs. 移動 (3:2, great)
ko: 더 보기 vs. 옮기기 (4:3, great)
en: More vs. Move (4:4, good)
zh-hans: 更多 vs. 移动 (2:2, good); zh-hant is the same, 更多 vs. 移動
it: Altro vs. Sposta (5:6, fine)
pt: Mais vs. Mover (4:5, fine)
pl: Więcej vs. Przenieś (6:8, close enough)

2x
sv: Mer vs. Flytta (3:6, poor)
fr: Plus vs. Renommer (4:8, poor)
nl: Meer vs. Hernoemen (4:9, poor)
de: Mehr vs. Verschieben (4:11, bad)

3+x
es: Más vs. Trasladar (3:9, bad)
ru: Ещё vs. Переименовать (3:13, very bad)

Could we get the translations improved to be briefer?

I'd recommend solving this via T24986. In which case it will naturally use whatever width it ends up having in the user's device. Regardless of localisation language and client font.