953070 - [B2G][Homescreen] UI can become unresponsive when the user quickly taps the update alert and then a collection icon

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Homescreen, defect)

Description

[Matthew Vaughan]

Attachment: Video of icons becoming unselectable.

Description:
The Homescreen UI can become unresponsive if the user taps the update alert that appears at the top of the screen and then quickly taps an app collection icon. Either all the icons on the Homescreen become unselectable, or the user is taken to the chosen app collection screen and is stuck there until the device is restarted.

When the icons become unselectable, the user is able to long tap them to go into editting mode but will not be able to do anything else after that.

Repro Steps:
1) Update Buri to 12/24 1.3 MOZ RIL BuildID: 20131224004001
2) Reset the device
3) During FTE, connect to WiFi and complete the FTE
4) While on the E.me screen, wait for the "1 update available" alert to appear
5) Quickly tap the update alert and then the Social collection icon

Actual:
All Homescreen UI becomes unresponsive. Keyboard may appear and then disappear quickly, if not remaining on the screen.

Expected:
User is taken to the Social collection screen. Keyboard is never displayed.

Environmental Variables:
Device: Buri v1.3 MOZ RIL
BuildID: 20131224004001
Gaia: 01e9da49be2cc4bc134eeefc434740d572ec2246
Gecko: af28fe58e263
Version: 28.0a2
Firmware Version: V1.2_US_20131115

Notes:
Repro frequency: 6/13
See attached: Unselectable_Icons.ogg

This issue does not seem to reproduce on the 12/24 1.2 or Master M-C (1.4) builds.

Comment 1

[Matthew Vaughan]

This issue seems to have started reproducing on the 11/25/13 1.3 build.

- Works -
Environmental Variables:
Device: Buri v1.3 MOZ RIL
BuildID: 20131124040202
Gaia: c736d91f6a1aada7b81a3d7b7df2635f2f9a655a
Gecko: 74ab61b8d0f0
Version: 28.0a1
Firmware Version: V1.2_US_20131115

- Broken -
Environmental Variables:
Device: Buri v1.3 MOZ RIL
BuildID: 20131125142741
Gaia: bd8053d30c275f8d3040cd494e04b3480a784656
Gecko: 757c2011df5b
Version: 28.0a1
Firmware Version: V1.2_US_20131115

Comment 2

[Gregor Wagner [:gwagner]]

Cristian, do you have any cycles for this?

Comment 3

[Cristian Rodriguez (:crdlc)]

Sorry guys but I cannot reproduce it :( at least until this moment when I am writing this comment. Although analyzing the video carefully, I think that you are not clicking on the update notification item but you are touching the evme search bar and immediately the collection. I am suspecting this because after clicking on search bar, icons disappear and the keyboard appears for a short time.

How it works... When you click on collections/icons in the grid, the tap action is disabled in the homescreen in order to avoid opening several apps at the same time under those conditions:

https://github.com/mozilla-b2g/gaia/blob/v1.3/apps/homescreen/js/page.js#L993

I suspect that ev.me loads all resources when the entryfield was clicked and there is a conflict between both actions (search and open collection) and not conditions are fired. Then you cannot click on icons/collections anymore (except if you click on home button thought).

Matthew,

   Did you check if the homescreen gets OK clicking on home button?
   Did you test if it is reproducible clicking on the top of the notification in order not to touch the entryfield?

Ran,

   Hey, could you take a look to this issue? or give your point of view?

Thanks in advance

Comment 4

[Ran Ben Aharon [:ranbena] EverythingMe]

Amir any thoughts on this?

Comment 5

[Amir Nissim (:amirn)]

Not able to reproduce on latest v1.3.

I am not getting any update alert after reset.

I did however try the following, which leads me to believe it is not related to the search bar:
1. reset the device
2. tap the searchbar
3. quickly tap a collection

the UI stays responsive (but laggy since e.me assets are loaded in the bg)

Comment 6

[Matthew Vaughan]

(In reply to Cristian Rodriguez (:crdlc)  (PTO 01-22 to 01-23) from comment #3)
> Matthew,
> 
>    Did you check if the homescreen gets OK clicking on home button?
>    Did you test if it is reproducible clicking on the top of the
> notification in order not to touch the entryfield?

When this issue reproduced, pressing the Home button would not fix it. I attempted reproducing this issue again and I can no longer get it to happen. I know APZ has been causing some interesting things to happen so I wonder if that had anything to do with it? But regardless, I am no longer able to reproduce this issue.

I am still seeing some lag with e.me though, similar to what Amir said in comment 5.

Comment 7

[Cristian Rodriguez (:crdlc)]

The lag with e.ve is how it works, I mean, ev.me is loaded in lazy mode when users try to search some term or open/create a collection. This lazy mechanism allows us to save a lot of memory in the app. I cannot no longer to reproduce it so IMHO we could close it, right?

Comment 8

[Jason Smith [:jsmith]]

Yup.