1152684 - [Window Management][Search] Rocketbar expanding/minimizing transition animation occurs underneath a dropdown menu screen

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

Description

[Verson Xiong (Leave from Mozilla)]

Attachment: video_1622.mp4

[1.Description]:
[Flame v2.2 & v3.0][Search]When user open rocketbar in value selector page, they will find background becomes value selector. 
Found time:16:22
See attachment:logcat_1622.txt & video_1622.mp4

[2.Testing Steps]: 
1.Open settings.
2.Navigation to Search and tap it.
3.Tap Search Engine selector.
4.Tap rocketbar.
5.Tap Close.
6.Repeat 4 ~5 and check background.

[3.Expected Result]: 
6.Background is always Settings page.

[4.Actual Result]: 
6.Sometimes background is value selector.

[5.Reproduction build]: 
Flame 2.2:   Affected
Build ID               20150408002503
Gaia Revision          ea735c21bfb0d78333213ff0376fce1eac89ead6
Gaia Date              2015-04-07 20:58:15
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/43041c78052b
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2

Flame 3.0:   Affected
Build ID               20150408160203
Gaia Revision          a290b11627ec2b7c25980f5687a98da86641cfe4
Gaia Date              2015-04-08 08:26:08
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/2c92a7df87c9
Gecko Version          40.0a1
Device Name            flame
Firmware(Release)      4.4.2

[6.Reproduction Frequency]: 
occasionally Recurrence,3/10

[7.TCID]: 
Free Test

Comment 1

[Verson Xiong (Leave from Mozilla)]

Attachment: logcat_1622.txt

Comment 2

[Hermes Cheng (inactive after July 27, 2015)]

Alive, based on your comment [1] at bug 1152251, verson found that the value selector does not always dismiss. Could you take a look?

@Verson, thanks!

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1152251#c3

Comment 4

[GitHub Autolander Bot]

Attachment: [gaia] KevinGrandon:bug_1152684_value_selector_rocketbar_request > mozilla-b2g:master

Comment 5

[Kevin Grandon :kgrandon]

Comment on attachment 8591862 [details] [review]
[gaia] KevinGrandon:bug_1152684_value_selector_rocketbar_request > mozilla-b2g:master

Alive or Tim - could either of you review this?

It seems that the current app does not receive a _inputmethod-contextchange for some reason. I'm not sure if this is a bug or not. Listening to global-search-request inside of the value selector code seems to work well. Let me know what you think, thanks!

Comment 6

[(inactive after 6/18) Alive Kuo [:alive]]

Comment on attachment 8591862 [details] [review]
[gaia] KevinGrandon:bug_1152684_value_selector_rocketbar_request > mozilla-b2g:master

Thanks for taking this. I'd rather not to put too much detail of window management inside value selector UI.

As you mentioned, 'input-contextchange' is triggered from the appWindow#blur when rocketbar is opened.

Rocketbar activated -> HierarchyManager -notify-> AppWindowManager -blur-> activeApp -> input-contextchange event -> HierarchyManager -> dispatch input-contextchange event to top most UI (should be rocketbar at this moment.)

So the real problem seems to be: hierarchy manager should just broadcast the blur event to all UI modules and just send focus to the top most UI module.

If this does not work, let's just hide the value selector when AppWindow#blur is called.

Talk to me if you have problems!

Comment 7

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Comment on attachment 8591862 [details] [review]
[gaia] KevinGrandon:bug_1152684_value_selector_rocketbar_request > mozilla-b2g:master

What Alive said :)

Comment 8

[Kevin Grandon :kgrandon]

Comment on attachment 8591862 [details] [review]
[gaia] KevinGrandon:bug_1152684_value_selector_rocketbar_request > mozilla-b2g:master

Alive - Here is a new approach, only manually blurring the active app during rocketbar window. I think this might be better for a few reasons:

- Timing is better than waiting for the blur() event. If we wait until handling the event from app_window_manager, it still causes the rocketbar to animate underneath the dialog as we don't call focus() on it until after rocketbar is expanded.

- Less chance of regression. This patch is much more simple and many less moving pieces than a larger refactoring.

Let me know what you think, I'm fine taking another stab at it if this is not satisfactory.

Comment 9

[(inactive after 6/18) Alive Kuo [:alive]]

All right, I think it's a little confused in my comment. We should not try to fire the event for gecko.
inputcontext-change is a mozChromeEvent caught from gecko -> gaia whenever focus/blur/textselection is triggered.

If we want to programmatically hide the value selector, let's use the 2nd way I said in the review comment:
in BrowserMixin#blur do this.valueSelector && this.valueSelector.hide();

With doing this, if blur here is not called when rocketbar is opened, we should check why.

Does this make it clear to you? I am fine to take this if you don't want to continue! :)

Comment 10

[GitHub Autolander Bot]

Attachment: [gaia] KevinGrandon:bug_1152684_rocketbar_activation_blur > mozilla-b2g:master

Comment 11

[Kevin Grandon :kgrandon]

Comment on attachment 8592263 [details] [review]
[gaia] KevinGrandon:bug_1152684_rocketbar_activation_blur > mozilla-b2g:master

Alive, here's my last attempt at this, if it's still insufficient you can steal it. We need to manually blur still, otherwise we don't get the blur event in time for the animation. I also tried using window.focus() instead of app.blur(), but that did not work.

Please take a look if you have time, thanks!

Comment 12

[(inactive after 6/18) Alive Kuo [:alive]]

Comment on attachment 8592263 [details] [review]
[gaia] KevinGrandon:bug_1152684_rocketbar_activation_blur > mozilla-b2g:master

Big thanks for your patience.

Comment 13

[Gregor Wagner [:gwagner]]

Do we still need this?

Comment 14

[Kevin Grandon :kgrandon]

(In reply to Gregor Wagner [:gwagner] from comment #13)
> Do we still need this?

Yes, but I've been having tons of trouble with the tests for some reason. Need to investigate further.

Comment 15

[BMO Automation]

Firefox OS is not being worked on