/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --autoplay-policy=document-user-activation-required --enable-audio-focus --enable-devtools-experiments --enable-fullscreen-tab-detaching --enable-google-branded-context-menu --enable-offer-store-unmasked-wallet-cards --enable-offline-auto-reload-visible-only --enable-offline-auto-reload --site-per-process --enable-tab-audio-muting --enable-web-authentication-testing-api --extension-content-verification=enforce_strict --load-media-router-component-extension=1 --reduced-referrer-granularity --tls13-variant=final --top-chrome-md=material-refresh --enable-features=AutofillUpstream,AutomaticTabDiscarding,Av1Decoder,BackgroundVideoTrackOptimization,BlockTabUnders,BrowserTouchBar,ContentFullscreen,DialogTouchBar,EnableEmojiContextMenu,EnableEphemeralFlashPermission,ExpensiveBackgroundTimerThrottling,FullscreenToolbarReveal,HappinessTrackingSurveysForDesktop,MarkHttpAs,NativeNotifications,NewStyleNotifications,NewTabPageBackgrounds,NewTabPageUIMd,NoStatePrefetch,OmniboxSpeculativeServiceWorkerStartOnQueryInput,OverflowIconsForMediaControls,ParallelDownloading,PasswordForceSaving,PdfIsolation,PolicyTool,RecurrentInterstitialFeature,RuntimeHostPermissions,SafeSearchUrlReporting,SingleTabMode,SiteSettings,SoundContentSetting,SpeculativePreconnect,TabStripKeyboardFocus,TextSuggestionsTouchBar,UseModernMediaControls,WebAuthentication,WebAuthenticationCable,WebAuthenticationCtap2,WebAuthenticationTouchId,WebPayments,WebPaymentsModifiers,brotli-encoding --flag-switches-end

Thanks for the report. CTRL-TAB is always cycling through the tabs 1-2-3-4-1-2-3-4. Never noticed another behavior?

Maybe you have an extension installed that provided it and doesn't work now?

I'm not aware of any extension that I have had installed on my system over the years that is responsible for that behaviour, and the same was experienced on chrome canary new blank profiles.

From muscular memory, chrome *used* open new tabs next to the current one (a big change from back in the days chrome and Firefox would always open a new tab at the end) and ctrl tab would jump between the two last used tabs.... 

I can't be going mad with this, can I? It's something I do daily via muscular memory, and after restarting chrome for m70 beta update stop working 

Tried checking the issue on reported chrome version 70.0.3538.16 using Mac 10.13.1 with the exact steps mentioned in comment#0.

Our Observations:
------------------
When multiple tabs are opened, then clicking ctrl+tab navigated to the next tab but not to the tab which was previously used(...as clearly said in Comment#2). As mentioned in C#0 that it worked earlier, but we didn't see the tabs getting switched to previously used one rather they navigated to the next tab. Similar behaviour is seen from M60(60.0.3112.0) hence removing Needs-Bisect label and requesting someone from respective team to have a look into this and help in further triaging it.

Thanks!

Could you try this?

1. Visit chrome://flags/#views-browser-windows
2. Set that flag ("Use Views browser windows instead of Cocoa.") to Disabled.
3. Click the "Relaunch Now" button which appears.
4. Test.
5. Repeat steps 1-3, but set the flag back to Default.

That UI is going to be removed soon and may no longer work reliably, but it should let you test for differences without tracking down an old version of Chrome.

Hi @sdy

changing chrome://flags/#views-browser-windows
to Disabled and restarting chrome didnt change the behaviour

/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --autoplay-policy=document-user-activation-required --enable-audio-focus --enable-devtools-experiments --enable-fullscreen-tab-detaching --enable-google-branded-context-menu --enable-offer-store-unmasked-wallet-cards --enable-offline-auto-reload-visible-only --enable-offline-auto-reload --site-per-process --enable-tab-audio-muting --enable-web-authentication-testing-api --extension-content-verification=enforce_strict --load-media-router-component-extension=1 --reduced-referrer-granularity --tls13-variant=final --top-chrome-md=material-refresh --enable-features=AutofillUpstream,AutomaticTabDiscarding,Av1Decoder,BackgroundVideoTrackOptimization,BlockTabUnders,BrowserTouchBar,ContentFullscreen,DialogTouchBar,EnableEmojiContextMenu,EnableEphemeralFlashPermission,ExpensiveBackgroundTimerThrottling,FullscreenToolbarReveal,HappinessTrackingSurveysForDesktop,MarkHttpAs,NativeNotifications,NewStyleNotifications,NewTabPageBackgrounds,NewTabPageUIMd,NoStatePrefetch,OmniboxSpeculativeServiceWorkerStartOnQueryInput,OverflowIconsForMediaControls,ParallelDownloading,PasswordForceSaving,PdfIsolation,PolicyTool,RecurrentInterstitialFeature,RuntimeHostPermissions,SafeSearchUrlReporting,SiteSettings,SoundContentSetting,SpeculativePreconnect,TabStripKeyboardFocus,TextSuggestionsTouchBar,UseModernMediaControls,WebAuthentication,WebAuthenticationCable,WebAuthenticationCtap2,WebAuthenticationTouchId,WebPayments,WebPaymentsModifiers,brotli-encoding --disable-features=ViewsBrowserWindows --flag-switches-end

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

mac triage: to sdy@ for followup

Assuming changing that flag also flipped Chrome back to the old UI, it sounds like behavior didn't change. Sorry to make you question your sanity! If you do find an older build that behaves the way you described, let us know.

@sdy i totally get that.
thanks for your time, team

Thanks, we appreciate the report regardless.