Page MenuHomePhabricator

Reorganize selection's context menu items, so that the "Copy" item is first and always visible
Open, Needs TriagePublicFeature

Assigned To
None
Authored By
trejder
Sep 21 2023, 6:21 AM
Referenced Files
F41590587: 05.jpg
Dec 10 2023, 4:28 PM
F41590585: 01.jpg
Dec 10 2023, 4:28 PM
F37745503: Screenshot_20230921-094725.png
Sep 21 2023, 7:59 AM

Description

Selecting any text in any Wikipedia article is in 75-90% of the scenarios done for copying it. Hiding "Copy" option in secondary level menu and forcing user to tap "→" each time they want to copy a text is a serious UX-bug.

I estimate (based on no research though) that we can split user intentions like that:

  • 75% want to copy selected text
  • 24% want to translate it
  • 1% want to start editing it using context menu

Users has "Pen" icon for that next to each section title to start editing, so number of them using context menu for that is negligible.

Putting "Translate" and "Edit here" in first level context menu and "Copy" in second level is a misunderstanding as for me (looking from UX perspective).

Steps to replicate the issue (include links if applicable):

  • Open any article in Android mobile application
  • Select any piece of text

What happens?:

The "Translate" and "Edit here" items are visible. The "Copy" item requires pressing "→" button.

What should have happened instead?:

The "Copy" and "Translate" items are visible. The "Edit here" item requires pressing "→" button.

Software version (skip for WMF-hosted wikis like Wikipedia):

  • Wikipedia for Android: 2.7.50452-r-2023-09-06
  • Phone: realme GT 5G (RMX2202)
  • Android: 13 Kernel version 5.4.147-qgki-ga616720f33728

Other information (browser name/version, screenshots, etc.):

Screenshot_2023-09-17-21-06-21-82_173823495e561b2cdc2de22ac640109c.jpg (699×1 px, 47 KB)

Screenshot_2023-09-21-07-32-15-65_173823495e561b2cdc2de22ac640109c.jpg (610×1 px, 56 KB)

Event Timeline

Aklapper changed the task status from Open to Stalled.Sep 21 2023, 7:59 AM

What happens?:

The "Translate" and "Edit here" items are visible. The "Copy" item requires pressing "→" button.

Not here. What makes you think this is any behavior that the mobile app itself could influence, and not your local mobile settings?

Screenshot_20230921-094725.png (1×720 px, 268 KB)

Well, I am old school dev, thinking that if anything appears in your_ app then you are responsible for this, sorry.

The assumption was also made because "Translate" is added to selected text's context menu in Wikipedia mobile app only. No other application that offers text selection (and a context menu for that selection) has this item.

Still, having "Edit Here" before "Copy" is pointless from UX perspective. The most often used item should always be first.

And I am pretty much sure that there are 25x more users willing to copy selected text than those that are selecting it to start editing an article.

So from this perspective my ticket seems valid. It is an UX bug that "Edit Here" goes first.

(this would also solve my issue, because stupid Google Translate's button would pushed "Edit Here", not "Copy" to the second level, but that's not a point here)

Aklapper changed the task status from Stalled to Open.Sep 22 2023, 3:29 PM
Aklapper changed the subtype of this task from "Bug Report" to "Feature Request".
trejder renamed this task from Reorganize selection's context menu items, so that the "Copy" item is always visible to Reorganize selection's context menu items, so that the "Copy" item is first and always visible.Sep 22 2023, 3:51 PM

You're both right - The order of the items in this context menu is partially under the system's control, and partially under our control, such that it may be possible for us to rearrange them.
I do agree that we should reevaluate the order of the items based on most likely user intentions, preferably supported by data with a citation ;)
We'll discuss with the team.

Bumping issue up after 2.5+ months of complete silence.

I understand that this may be a very low level or even stupid feature request to some. But... believe me or not... 95% of people around the world is really selecting text in your app to COPY it. Not to:

  • Share it
  • Read it aloud
  • Search it in Edge
  • Define its meaning
  • Edit the article starting from this point

The Copy item must unconditionally be the first one. Making it fifth is pointless, non-sense, sad, meaningless and disappointing.

And it really doesn't matter, if this is caused by system, Wiki app or current star configuration in the sky above Honolulu.

This is because we're talking about UX, not about technical stuff. And UX clearly says that 95% of millions around the world is selecting text to copy it.

Really, honestly, believe me.

I really, really believe that the above assumption is self-proving. And while I recognize and understand the need for UX exercises with questions, forms, data and citations. But I hope that in this single case we can make an exception and... assume the above. And we don't have to ask 100 people on the main streets of our cities, why did you select the text when you read it. I hope...

01.jpg (2×1 px, 828 KB)
05.jpg (2×1 px, 543 KB)