This is always the case. Tested on M60.0.3112.72 and the behavior is same.

I wonder if this is simply because we trigger -tabWasTapped on touchUpInside instead of  touchDown.  rohitrao@ any historical reason why we trigger this on touchUp?  It looks like most other browsers (desktop, safari, etc) go with touchDown.

srikanthg@ Lets try this on a dev build with touchDown and see if you still see the difference (rather than landing this change for now)

Does touchDown make a difference?  Does the video show a touch+drag?  Why is touchUpInside being delivered at all in that case?

I probably used touchUpInside because that's what we do for other buttons.  It's ok to change if we think touchDown would be better.  Right now can you longpress+drag to reorder a tab without selecting it?  We'd lose that if we switched.

>  We'd lose that if we switched.
That's correct -- longpress + drag on desktop also selects first.

If you have a dev build with the CL, then please share it on Google Drive, so that I can take a look test your change.

+edchin for snapshot question

Turns out snapshots are really slow here.

Do we need tab_strip_controller::-tabViewTapped to take a snapshot?  Note, we won't take that snapshot when changing tabs from the keyboard, or from swipe gestures, etc.

eugenebut@, shbarezer@, and I just looked at this on real iPad devices with M70+ and were not able to repro the lag. The switching was fast and expected. I'll capture video.

Did a VC with edchin@ to explain the issue, and filed 905065 for investigation.