+hannahs@ and +austinknight@ for UX input on this feature request to update our long-press context menu to:
 - move "Open in other window" lower in the menu (after Open in incognito)
 - add a new option that's only present if the user already had a tab with the same URL opened that takes them to that tab

Moving down "open in other window" seems reasonable given the low usage of multi-instance mode. 


Re-focusing a tab that contains the same URL a the one just long-pressed seems like a power feature that may not weigh out against making the context menu longer. I know we worked hard to get the context menu shorter so that it's easier simpler and easier to use.

> Re-focusing a tab that contains the same URL a the one 
> just long-pressed seems like a power feature that may 
> not weigh out against making the context menu longer. 
> I know we worked hard to get the context menu shorter 
> so that it's easier simpler and easier to use.

Thank you for your comment. I think that everything depends on usage pattern. When you have few tabs, you won't see any problem... but when you have 50 or more tabs (typical case for me) seeing duplicates and closing them is a pain. 

There is general tendency to decrease resources usage and helping users eliminate duplicates is really good idea especially on devices with smaller capabilities.

Please also note, that normal user probably won't see this option at all, people like me will be happy to have it (and it's just one option and it seems to be low price which we pay)

I have 2 questions right now:

1. if this is not good for you to have it in mainstream - will you accept it with flag (enabled with chrome://flags) ? can we get some decision quite fast here?

2. who could help me in other context menu changes as well? I would like to fix the most annoying problems and I want to move forward, unfortunately it looks that without concrete person it's difficult (for example shortening URLs required more than that year, because nobody was able to make decision)

In general, I would suggest splitting up both your CL and this bug in two, because the two features seem pretty independent, and it just complicates discussions to have both of them together.

I'll ultimately defer to PMs / UX on your questions, but one thing I can say is that chrome://flags is not meant as an "advanced settings" section -- it allows testing features that aren't quite ready yet for everyone.

+Yusuf, who is working in the area of tab / task management.

Thank you Bernhard,

I will of course split it if necessary.

I agree that flags were not designed as an "advanced settings" section, from the second hand new context menu stays there for years (?).

Let's move now with this and let's show "yes ! we can!", all help appreciated.

I've tried to contact people from #6, unfortunately without result.

Could you ask any UX for looking it please?

I've tried to contact people from #6, unfortunately without result.

Could you ask any UX for looking into it please?

Moving "Open in other window" lower in the menu (after Open in incognito) sgtm.

I also agree with Theresa on the shorter context menu. We are however, considering other explorations for switching to Incognito mode which may address. Will follow up here once we know more.

Thanks!

hannahs@ -> if we're so thinking about length of menu, what about replacing "Open in new tab" with "Switch to tab" (when browsing in normal mode) and replacing "Opening in incognito tab" with "Switch to incognito tab" (when browsing in incognito mode) ?

if not, will you be OK for adding it as experiment in chrome://flags for further discussion?

"Switch to tab" would be a new browser feature for a less common use case, and as such I don't think we would want to remove "Open in new tab" in favor of it.

Unfortunately, I don't think this is a case where it would be worth it either to move this into chrome://flags temporarily until we have fixed some small details -- at the moment this looks like a feature that is too niche to find its way into Chrome, and without a way looking forward for the feature to graduate, chrome://flags isn't a place for it either.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ecd9128dca4c846b36af498dbb6be1d3cc5eb7e6

commit ecd9128dca4c846b36af498dbb6be1d3cc5eb7e6
Author: Marcin Wiacek <marcin@mwiacek.com>
Date: Tue May 29 12:45:41 2018

Move "Open in other window" down in context menu

Patch is moving "Open in other window" in the context menu
below "Open in (incognito) tab" options.

BUG=845335

Change-Id: I6c4a9453d45d68d97cdbfdf023840a527ae30cc8
Reviewed-on: https://chromium-review.googlesource.com/1076129
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Marcin Wiącek <marcin@mwiacek.com>
Cr-Commit-Position: refs/heads/master@{#562395}
[modify] https://crrev.com/ecd9128dca4c846b36af498dbb6be1d3cc5eb7e6/chrome/android/java/src/org/chromium/chrome/browser/contextmenu/ChromeContextMenuPopulator.java

If something is a less common use case, why we so much care about size of context menu?

I gave option A (adding "Switch to tab") and it's bad, I give option B (replacing "Open in new tab" with "Switch to tab") and it's also bad.

If this is not affecting many users, why can't we agree for it? Why can't we help users, who are opening many tabs?

Chrome should move browsing forward, we have similar options in browsers and I really don't understand, why can't have neither option A and option B in the mobile devices, which are not powerful.

Why are we so conservative?

When we speak about moving forward: I've opened https://bugs.chromium.org/p/chromium/issues/detail?id=847454 and would like to spend some time to make interface more consistent, just need UX approval.

Hi all,

I have new proposal for these scenarios, please add yourself to the https://bugs.chromium.org/p/chromium/issues/detail?id=882267 if you're interested.

With kind regards,
Marcin