Mark Hammond [:markh] [:mhammond] Reporter
	Description • 10 years ago

STR:
* Open about:preferences leaving it on the "general" tab.
* Switch to another tab.
* Exit Firefox
* Restart Firefox - note that about:preferences is now in a yet-to-be-loaded ("unloaded"?) background tab.
* Arrange for "openPreferences()" to be called - eg:
** Arrange for the "Choose what I share" telemetry infobar to appear and click the button
** Arrange for the sync error pane with the "Preferences" button to appear and click it
** Easier still - in a browser scratch-pad, execute:
 Services.wm.getMostRecentWindow("navigator:browser").openPreferences("paneSync")

Expected:
* Tab with about:preferences is made current and the "sync" pane is showed

Actual:
* Tab with about:preferences is made current, but "General" remains selected.  Browser scratchpad reports:

Exception: browser.contentWindow.selectCategory is not a function
switchToPane@chrome://browser/content/utilityOverlay.js:493:9
openPreferences@chrome://browser/content/utilityOverlay.js:507:7
@Scratchpad/1:13:1
WCA_evalWithDebugger@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webconsole.js:1065:7
WCA_onEvaluateJS@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webconsole.js:730:9
DSC_onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js:1151:9
LocalDebuggerTransport.prototype.send/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/transport/transport.js:540:11
makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:84:7

Note that it works fine if about:preferences is already fully loaded in either the selected or a non-selected tab.

cc jaws: Looks a little like bug 1020245, but that's marked as fixed and doesn't seem identical.

	Jared Wein [:jaws] (please needinfo? me)
	Comment 1 • 10 years ago

The gotoPref call in utilityOverlay.js was obsolete now that the preference category is included in the URL hash.

	Tim Taubert [:ttaubert] (inactive)
	Comment 2 • 10 years ago

Comment on attachment 8443272 [details] [diff] [review]
Patch

Review of attachment 8443272 [details] [diff] [review]:
-----------------------------------------------------------------

AFAICT gotoPref() still exists, wouldn't it be better to use that? openPreferences() would simply need to handle pending tabs, probably in the same "advanced-pane-loaded" observer.

	Jared Wein [:jaws] (please needinfo? me)
	Comment 3 • 10 years ago

(In reply to Tim Taubert [:ttaubert] from comment #2)
> Comment on attachment 8443272 [details] [diff] [review]
> Patch
> 
> Review of attachment 8443272 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> AFAICT gotoPref() still exists, wouldn't it be better to use that?
> openPreferences() would simply need to handle pending tabs, probably in the
> same "advanced-pane-loaded" observer.

gotoPref still exists, but once the tab gets switched to it starts a race with the browser.loadURI code. If the browser.loadURI code kicks off first (which it seems to do in all of my testing), then the expected URL is overwritten by the restored URL from SessionStore.

The attached patch still has the same issue of gotoPref but now with switchToAdvancedSubPane.

	Mark Hammond [:markh] [:mhammond] Reporter
	Comment 4 • 9 years ago

This was fixed by bug 1100223.

I do still get:
Exception: TypeError: browser.contentWindow.gotoPref is not a function
openPreferences@chrome://browser/content/utilityOverlay.js:530:9
@Scratchpad/1:1:1

But everything seems to work fine.

	[SV Manager] Florin Mezei, QA (:FlorinMezei)
	Comment 5 • 9 years ago

There doesn't seem to be any more manual QA needed here since Mark confirmed this in comment 4. Setting as qe-verify+. Fell free to set it back if you think otherwise.