Closed Bug 575273 Opened 14 years ago Closed 13 years ago

Cannot type in adressbar after session restore

Categories

(Firefox :: Session Restore, defect)

3.6 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: sinaasappeljam, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6 ( .NET CLR 3.5.30729)

After starting up the browser with restore last session enabled, I cannot type in the adressbar or the Googlebar. To fix this I have to minimize and restore the window. Then it works again.

Reproducible: Always

Steps to Reproduce:
1. Enable session restore. 
2. Open a number of websites in tabs (mine has 9 now)
3. close the browser.
4. Start up the browser
5. open a new tab
6. type in an url in the adressbar ---- dont work
7. minimize the window
8. restore the window
9. type in an url in the adressbar - works!
Actual Results:  
In the adress bar and google bar there is inverted text. Everything typed over it is ignored.

Expected Results:  
accept an url or search argument the first time
Component: Toolbars → Location Bar
QA Contact: toolbars → location.bar
Version: unspecified → 3.6 Branch
Firefox 4 has a better handling of session restore, so you could give it a try and report back if it's any better in your case.
Component: Location Bar → Session Restore
QA Contact: location.bar → session.restore
Reporter -> Are you still experiencing this issue with the latest version of Firefox 3.6.16? Does the issue occur with Firefox 4? Does the issue occur with the latest nightly? http://nightly.mozilla.org/
Closing bug as Incomplete - if you are still experiencing this issue or have more information to provide feel free to post back here and we can re-open the bug. You can also get assistance by visiting the Firefox help site -> http://support.mozilla.com/en-US/kb/Ask+a+question
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.