Home button is not work well in Firefox OS 2.5 Simulator. It is same result when I push 'Home' Key. I reproduced this phenomenon in Win/Mac. Reproduce Step: 1) Open Firefox OS 2.5 Simulator.(I use Nightly[2015-07-29] Object) 2) Open Setting app. 3) Tap Home Button. Expected Result: Go to the Home Application. Actually Result: Can't go to the Home Application.
I checked that process of Home button. It was controlled by /b2g/chrome/content/desktop.js. Latest change of this file is bug 1074180. I reverted this bug changeset. Then it work well on Home Button. jryan: bug 1074180 is fixed Firefox e10s issue. Is it necessary to b2g-desktop?
Thank you for investigating the regression! I can reproduce the issue, so hopefully I can take a look soon.
Assignee: nobody → jryans
Status: NEW → ASSIGNED
In my own testing, pressing the Home key on the keyboard does go back to the home screen correctly. Only clicking the Home button in the UI is failing. Does the Home key on the keyboard work for you? I wasn't sure from comment 0. I am testing on Mac at the moment.
(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #3) > In my own testing, pressing the Home key on the keyboard does go back to the > home screen correctly. > > Only clicking the Home button in the UI is failing. > > Does the Home key on the keyboard work for you? I wasn't sure from comment > 0. > > I am testing on Mac at the moment. jryans, Thank you for your reply. But, keyboard does go back when click any chrome position.(e.g. Rotate Button) I recorded this phenomenon video. 00:00-00:16 : Keyboard works well. But, keyboard does go back when click any chrome position.(e.g. Rotate Button) This behavior is same before Firefox OS 2.2 Simulator. 00:16-Last : This phenomenon. Setting Apps doesn't go back when click Home button.
Ah, I mean the physical Home key on your computer's keyboard, not the on-screen keyboard inside the simulator. The physical Home key can be pressed as an alternative to the currently broken button in the simulator UI. So far I think we are seeing the same thing, so I'll move forward with my fix.
After bug 1074180, the touch event simulator only affects the simulator's content window, so the UI chrome is no longer covered. Switching back to mouse events seems to fix the buttons.
Attachment #8643481 - Flags: review?(poirot.alex) → review+
You need to log in before you can comment on or make changes to this bug.