Closed
Bug 978580
Opened 12 years ago
Closed 12 years ago
29a2: New private window urlbar without focus when "browser.newtab.url", "about:blank"
Categories
(Firefox :: Private Browsing, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: persona, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140302004001
Steps to reproduce:
Open a new private window via Shift-Ctrl-P
Actual results:
A new private window opens, but there is no focus. So I have to click into the adress bar to enter a URL.
Expected results:
After opening the new private window the cursor should stay in the address bar. If I open a new *standard* window I immediately can enter a new URL.
WFM on Mozilla/5.0 (Windows NT 6.3; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140302004001 CSet: 0f0ec964befb.
Please try Firefox Safe Mode or any more info.
Flags: needinfo?(persona)
I found the cause of the issue: its the line
user_pref("browser.newtab.url", "about:blank");
I found in my prefs.js. After deleting this line everything works as expected.
Flags: needinfo?(persona)
(In reply to persona from comment #2)
> I found the cause of the issue: its the line
> user_pref("browser.newtab.url", "about:blank");
> I found in my prefs.js. After deleting this line everything works as
> expected.
I reproduce the on Mozilla/5.0 (Windows NT 6.3; rv:29.0) Gecko/20100101 Firefox/29.0 ID:20140303004002 CSet: d60e6d4024e7
Not reproducible with Firefox 28.0b7.
Status: UNCONFIRMED → NEW
Component: Untriaged → Private Browsing
Ever confirmed: true
Summary: 29a2: New private window without focus → 29a2: New private window urlbar without focus when "browser.newtab.url", "about:blank"
Comment 4•12 years ago
|
||
This is a known issue, which we have decided not to be worth fixing. We have a whitelist of URLs which we use to decide if we need to focus the location bar based on, and about:blank is not on that list.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•