769530 - Google Images - Tablet image result pinwheel UI does not display properly in Fennec

Status: RESOLVED DUPLICATE of bug 793216

(Firefox for Android Graveyard :: General, defect)

Description

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Attachment: Desktop Firefox layering issue

Reproduction steps using an Android Tablet:
1) Open Fennec.
2) Click URL bar and open "images.google.com".
3) Enter "Firefox" (or other values) in the search bar and hit enter.
4) Click on the first image result.

Expected: The first image result, centered on screen.
Received: Another image result (third, in my case) shifted to the left.

5) Swipe right to advance to the next image (four image result comes up for me).
6) Swipe right again to advance to the next image (fifth image result for me).

Expected: The third image, centered on screen.
Received: The fifth image, layered on the fourth image, shifted to the left.

I believe there is also a missed animation though I do not have an iPad to check.

Desktop Firefox 13.0.1 (Mac OS 10.7.4 with the User Agent Switcher add-on spoofing iPad) appears to do the same layering, though unlike Fennec, the first image appears when the first image is clicked. The bug may need to be reclassified because of this issue.

Tested on Asus Transformer Prime TF201, Android 4.0.3, and Galaxy Nexus, Android 4.0.4 with Phony (using the "Android (Tablet)" profile).

Comment 1

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Attachment: Android on Tablet after first image click (displays third image)

Comment 2

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Attachment: Android on Tablet after two swipes (displays fifth image, stacking previous images)

Comment 3

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Adding reference to bug 638827 which is the phone version (which uses a different UI).

Comment 4

[Alexandre Folle de Menezes]

I can reproduce this on a Galaxy Tab 2 running Android 4.1.1.  It works fine on my desktop and Galaxy S2. All running Firefox 20.

This seems to be related to bug 793216.

Comment 5

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Forward duping to bug 793216 because some research has already been done for this issue in that bug.