Closed
Bug 404597
Opened 18 years ago
Closed 15 years ago
when working with dual monitors a new window fails to allow text entry into address bar or form elements
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: keran.mckenzie, Unassigned)
Details
(Whiteboard: [closeme 2010-02-10])
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b1) Gecko/2007110903 Firefox/3.0b1
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b1) Gecko/2007110903 Firefox/3.0b1
I downloaded and installed firefox 3 on OS X 10.4
I opened up one firefox window in my primary monitor (external monitor on laptop)
I then opened a new firefox window to drag to my secondary monitor (laptop monitor)
I attempted to type a URL into the address bar in the 2nd window (on secondary monitor) and I couldn't
I typed in first window - no problems
Drag the second window back to primary monitor - can type again, drag back to secondary monitor - can't type
Reproducible: Always
Steps to Reproduce:
1) open firefox in primary monitor
2) create a new firefox window
3) drag new window to secondary monitor
4) try to type URL into secondary window on secondary monitor
Actual Results:
No ability to type in Address bar, Google Search box or any form element on web page within secondary window
Expected Results:
Normal functionality of browser
Performed on MacBook Pro (intel) running OS X 10.4
External monitor = Dell LCD, functioning as Primary Monitor
Laptop Monitor = functioning as secondary monitor
Comment 1•16 years ago
|
||
reporter, do you still see this problem in version 3.5 or newer?
Whiteboard: [closeme 2010-02-10]
Comment 2•15 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•