943181 - Homescreen ignores touches of app buttons after an app fails to launch

Status: RESOLVED WONTFIX

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

Description

[Jed Davis [:jld] ⟨⏰|UTC-8⟩ ⟦he/him⟧]

Copying from bug 936169 comment 7:

> The homescreen app seems to get confused when it tries to start an app that doesn't actually start, because then it stops responding to clicks on any icon in the same page (or the strip at the bottom, if it was one of those) as the failed app.  Locking/unlocking the phone resets it; switching to and from a running app might also.


Context: In bug 936169, I was trying to make sure we did the right thing if we encounter an IPC error while starting a child process; I had a local change that killed the content process at the end of the ContentParent constructor (if the pid was within a certain range; it's not helpful if we prevent the Homescreen from starting!) to test this case.  I ran into some system-level issues which still need to be fixed (bug 943170 and bug 943174; the latter is probably harmless), but with workarounds for them I also saw this issue.

I'm guessing that the homescreen is trying to prevent the user from accidentally launching another app (or launching the same app twice, if that's possible) while the first one starts, but I don't know the code well enough for it to be obvious where to start looking.

Comment 1

[Kevin Grandon :kgrandon]

Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.