From our other projects around task continuity and the tablet UI redesign, we deliberately specified the ratio of the tab preview in the tray. These specific proportions were decided on because we thought it improved the UX of tab switching, and recalling which tab was what. We took the proportions of a range of devices and arrived at a divisible, "lowest-common-denominator" value for the width and height that provided a preview which closest resembled device screen dimensions. Since mobile has a very different form factor and typical usage "environments". We should take the same approach. I'd like to see how something like this would work. Without sacrificing how many tabs are displayed at once, we're able to show a more accurate depiction of what's on the screen. Could we get a build to test this Martyn?

I tested the build with my HTC M8, Lollipop Firs time I opened the tab tray, some of the inside of the tiles were stretched. However I can't reproduce it after. Next time the tab tray is open, all seems fine. screenshots attached

streched

bbermes: had you previously installed any of my other apks? If o it may have been the old images showing up initially. If not then it's something we'll have to keep our eyes out for, as I've not seen this before or been able to reproduce.

Here's a bit of playing around I've been doing. This is an aspect ratio of 1.2

Another with an asepct ratio of 1.35

This bug was getting confusing for me, moving this to block "V3" since this isn't in the scope for our first batch of updates.

Hola, not sure if you were able to join the Funnel meeting today, Martyn, but we agreed to put all Tabs Tray work behind a nightly flag. Antlam mentioned this specific bug is not behind a nightly flag yet, would you mind doing so, so we can combine/bundle this all together as one feature and its corresponding bugs for the nightly flag. Thanks

To be clear. This specific bug is for the NEXT iteration of this "better tab previews" work (so it's blocking "V3"). But I'm not sure where the "V2" iteration of this work was being tracked. Maybe Martyn can help point us in the right direction. It might have been looped into bug 1193745.

You're looking for bug 1193374

Unassigning until we start to work on "tabs-tray-v3".

I noticed this is still in 44 in Aha, I assume this won't ship for 44 then?

(In reply to Barbara Bermes [:barbara] from comment #12) > I noticed this is still in 44 in Aha, I assume this won't ship for 44 then? Correct, nothing shipping here.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.