1205264 - Write a test that tests behavior Browser app behavior with multiple windows and launching from homescreen

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::UI Tests, defect)

Description

[Martijn Wargers (dead)]

Follow-up from bug 1203060, see bug 1203060, comment 14:

The current behavior of the Browser app is when we have multiple browser instances in the background and then we tap on the homescreen, the most recent one that was displayed, gets displayed again.
This is not the case with a browser that for which the start page is open. In that case, the browser window before that gets opened.
Also, there can only be one browser window open with a start page, I noticed.

We should have a test for this that exercises this behavior.

Comment 1

[Martijn Wargers (dead)]

(In reply to Martijn Wargers [:mwargers] (QA) from comment #0)
> Also, there can only be one browser window open with a start page, I noticed.

I wrote this down in bug 1169010, comment 15:
Alberto, another thing I noticed:
- Open a browser window, go to some url, e.g.: "http://nu.nl"
- Open a new window, you get a the newtab page with "Top Sites" and "New private window" button
- Touch the home button
- Tap on the Browser icon

Now you get back to the browser window with the "http://nu.nl" page instead of the newtab page.
Is that expected behavior?
(I'm currently not even sure if this behavior is expected)

Comment 2

[Martijn Wargers (dead)]

Btw, I don't think our current locators in Browser/Search app are capable of handling multiple windows.
See:
http://mxr.mozilla.org/gaia/source/tests/python/gaia-ui-tests/gaiatest/apps/search/app.py#13
http://mxr.mozilla.org/gaia/source/tests/python/gaia-ui-tests/gaiatest/apps/search/regions/browser.py#11

They just take the first browser with those locators. But once the Browser/Search app has launched/pointed to a browser instance, it should use that instance.

Example of the dom of the various browser windows:

displayed newtab browser window:
<div aria-hidden="false" loading-state="false" style="background-image: none; background-size: 120px 120px; width: 320px; height: 569.333px;" data-manifest-name="Browser" class="appWindow render active search-app collapsible scrollable light" id="AppWindow_8" transition-state="opened">

hidden browser window:
<div aria-hidden="true" loading-state="false" style="background-image: none; background-size: 120px 120px; width: 320px; height: 569.333px;" data-manifest-name="Browser" class="appWindow render collapsible light browser scrollable inactive" id="AppWindow_4" transition-state="closed">

hidden private browser window:
<div aria-hidden="true" loading-state="false" style="background-image: none; background-size: 120px 120px; width: 320px; height: 569.333px;" data-manifest-name="" class="appWindow browser private collapsible render inactive" id="AppWindow_7" transition-state="closed">

Comment 3

[Martijn Wargers (dead)]

To be more clear in comment 2:
If there are already multiple browser windows in the background and then you do something like:
search = Search.launch()
It will open the last opened browser window.
The code in the search app object looks for the first element that matches the selector, but that might not be the last opened browser window at all.

Comment 4

[Martijn Wargers (dead)]

Marking WONTFIX, sorry for the bug spam. If somebody still wants to work on this, please file a new bug for it.