User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20100401 Firefox/3.6.3 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11) Gecko/20100401 Firefox/3.6.3 ( .NET CLR 3.5.30729) Occasionally after opening a new tab or window, the url bar will not allow me to type into it even though it's selected by default with the cursor in it when the new window/tab opens. Hitting ctrl-l or clicking on the url bar does not help, you must click elsewhere, then resrlect the url bar to begin typing. Reproducible: Couldn't Reproduce Steps to Reproduce: 1.Hit ctrl-t or ctrl-n 2.Start typing web address 3. Actual Results: No text is printed to the url bar Expected Results: Whatever I type shows up in the url bar This has been happening in my linux installation as well, but I recently installed the developer version Namoroku(sp?) and that seems to have triggered it there. It's quite rare, happens maybe once or twice a week, and spent some time trying to make it happen on demand but couldn't.
Do you have a plug-in like Adobe Reader (pdf) or such in some other tab? Looks like something is stealing focus here.
(In reply to comment #1) > Do you have a plug-in like Adobe Reader (pdf) or such in some other tab? Looks > like something is stealing focus here. This problem seems to have disappeared now. I don't even have my XP installation anymore, and my Linux install is also completely changed, after reinstalling to a newer distro. I am aware that plugins can largely cause this kind of problem, flash frequently grabs things from me.However This would happen upon creating a new tab or window with a hotkey where my starting page is about:blank, so the browser itself must have had focus to catch the hotkey, and there should be nothing on the new tab/window to steal it after that. Like I said though, this problem is gone for me since I've reinstalled everything. I don't know if anyone else is experiencing it, so feel free to close this if you feel like it's not an issue.
not reproducible anymore
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.