Closed
Bug 1087303
Opened 11 years ago
Closed 11 years ago
Add test for the functionality of remaining Panel Menu buttons in Australis (fullscreen, preferences)
Categories
(Firefox :: Toolbars and Customization, defect)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
FIXED
Firefox 36
Tracking | Status | |
---|---|---|
e10s | - | --- |
People
(Reporter: mihaelav, Assigned: mihaelav)
References
Details
(Whiteboard: [sprint])
Attachments
(1 file, 1 obsolete file)
4.96 KB,
patch
|
Gijs
:
review+
|
Details | Diff | Splinter Review |
This is a follow up of bug 947914, but for the remaining buttons: preferences, fullscreen and new 10s window.
Steps:
1. Start Firefox
2. Open the Panel Menu
3. Click on "New E10 Window", "Fullscreen" and "Preferences" buttons in the Panel Menu
Expected result:
Each button should perform the right corresponding action
Updated•11 years ago
|
tracking-e10s:
--- → -
Updated•11 years ago
|
Assignee: nobody → mihaela.velimiroviciu
Status: NEW → ASSIGNED
Whiteboard: [sprint]
Assignee | ||
Comment 1•11 years ago
|
||
When I'm trying to access the "New E10s window" button from a browser-chrome test the button is not found, although it exists there if I manually check it (for the same build). Can someone give a hint on why I can't access that button in the test, please?
Thanks!
Comment 2•11 years ago
|
||
(In reply to Mihaela Velimiroviciu [QA] (:mihaelav) from comment #1)
> When I'm trying to access the "New E10s window" button from a browser-chrome
> test the button is not found, although it exists there if I manually check
> it (for the same build). Can someone give a hint on why I can't access that
> button in the test, please?
> Thanks!
Hey Mihaela - I actually recommend not testing the New E10s window button, since this button is not supposed to make it to release. It's temporary while we do nightly testing of E10s.
Assignee | ||
Comment 3•11 years ago
|
||
Tests for fullscreen and preferences buttons
Attachment #8512669 -
Flags: review?(gijskruitbosch+bugs)
Assignee | ||
Updated•11 years ago
|
Summary: Add test for the functionality of remaining Panel Menu buttons in Australis (new e10s window, fullscreen, preferences) → Add test for the functionality of remaining Panel Menu buttons in Australis (fullscreen, preferences)
Comment 4•11 years ago
|
||
Comment on attachment 8512669 [details] [diff] [review]
v1
Review of attachment 8512669 [details] [diff] [review]:
-----------------------------------------------------------------
Thanks for pursuing this!
::: browser/components/customizableui/test/browser_1087303_button_fullscreen.js
@@ +1,3 @@
> +/* This Source Code Form is subject to the terms of the Mozilla Public
> + * License, v. 2.0. If a copy of the MPL was not distributed with this
> + * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
Nit: unless you mind licensing this public domain, could you get rid of the license header?
@@ +13,5 @@
> +
> + let fullscreenButton = document.getElementById("fullscreen-button");
> + ok(fullscreenButton, "Fullscreen button appears in Panel Menu");
> +
> + if(isOSX) {
Can we please skip-if = os == "mac" in browser.ini instead? :-)
::: browser/components/customizableui/test/browser_1087303_button_preferences.js
@@ +1,3 @@
> +/* This Source Code Form is subject to the terms of the Mozilla Public
> + * License, v. 2.0. If a copy of the MPL was not distributed with this
> + * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
Nit: unless you mind licensing this public domain, can you get rid of the license header?
@@ +13,5 @@
> +add_task(function() {
> + info("Check preferences button existence and functionality");
> +
> + initialPrefValue = Services.prefs.getBoolPref(PREF_INCONTENT);
> + Services.prefs.setBoolPref(PREF_INCONTENT, "true");
no quotes for true
@@ +26,5 @@
> + newTab = gBrowser.selectedTab;
> + yield waitForPageLoad(newTab);
> +
> + let prefsPage = gBrowser.selectedBrowser.contentWindow.document.
> + getElementById("categories");
This will fail on e10s. I'm enabling these tests in e10s mode by default in bug 1080787. Please test this some other way, like by checking the selectedBrowser's currentURI. :-)
@@ +31,5 @@
> + ok(prefsPage, "Preferences page was opened");
> +});
> +
> +add_task(function asyncCleanup() {
> + gBrowser.addTab(initialLocation);
Why do you need to add a new tab?
@@ +36,5 @@
> + gBrowser.removeTab(gBrowser.selectedTab);
> + info("Tabs were restored");
> +
> + // restore the browser.preferences.inContent preference
> + Services.prefs.setBoolPref(PREF_INCONTENT, initialPrefValue);
No need to save the value, use Services.prefs.clearUserPref(PREF_INCONTENT) instead.
@@ +44,5 @@
> + let deferred = Promise.defer();
> +
> + let timeoutId = setTimeout(() => {
> + aTab.linkedBrowser.removeEventListener("load", onTabLoad, true);
> + deferred.reject("TabSelect did not happen within " + 20000 + "ms");
You're waiting for load, but this says tabselect? That doesn't sound right...
Attachment #8512669 -
Flags: review?(gijskruitbosch+bugs) → feedback+
Just a drive-by note while looking through try for unrelated reasons:
The bug number in this patch is incorrect, and should be fixed before this lands.
Assignee | ||
Comment 6•11 years ago
|
||
(In reply to :Gijs Kruitbosch from comment #4)
> @@ +31,5 @@
> > + ok(prefsPage, "Preferences page was opened");
> > +});
> > +
> > +add_task(function asyncCleanup() {
> > + gBrowser.addTab(initialLocation);
>
> Why do you need to add a new tab?
If only one (about:blank) tab is opened when the test starts, the about:preferences page will load in that tab, and when I close it at the end, it closes the browser.
I added a check for gBrowser.tabs.length == 1 and added an about:blank tab if true, instead.
(In reply to Wes Kocher (:KWierso) from comment #5)
> Just a drive-by note while looking through try for unrelated reasons:
> The bug number in this patch is incorrect, and should be fixed before this
> lands.
Also updated the bug number in the patch, thanks for the notice.
Attachment #8512669 -
Attachment is obsolete: true
Attachment #8513455 -
Flags: review?(gijskruitbosch+bugs)
Comment 7•11 years ago
|
||
Comment on attachment 8513455 [details] [diff] [review]
v1.1
Review of attachment 8513455 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good, but can you trypush against current fx-team tip, and retrigger, esp. on linux? Thanks!
Attachment #8513455 -
Flags: review?(gijskruitbosch+bugs) → review+
Assignee | ||
Comment 8•11 years ago
|
||
Assignee | ||
Comment 9•11 years ago
|
||
There are no failures in the added tests.
Marking for checkin.
Keywords: checkin-needed
Comment 10•11 years ago
|
||
Comment 11•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [sprint][fixed-in-fx-team] → [sprint]
Target Milestone: --- → Firefox 36
You need to log in
before you can comment on or make changes to this bug.
Description
•