Closed
Bug 211941
Opened 21 years ago
Closed 21 years ago
Dual monitor: CSS Hover Inconsistent
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 159277
People
(Reporter: webguru12, Unassigned)
References
()
Details
(Whiteboard: DUPEME)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Example Location: http://www.iomega.com/global/index.jsp Summary: This problem occurs when on a secondary monitor to the left of the 0,0 axis (negative coorinates). Example Description: When hovering your mouse over the regions listed in the left navigation or over the map areas in the main body of the page, the hover event fires and then terminates prematurely. This can make certian types of DHTML menus very difficult to use. Reproducible: Always Steps to Reproduce: 1. Place browser on secondary monitor to the left of the 0,0 axis 2. Load page: http://www.iomega.com/global/index.jsp 3. Place mouse over North America region of the map or the text in left navigation 4. Notice the early termination of the hover event Actual Results: The hover event fires and ends prematurely. Expected Results: While the mouse is still over the object with the hover attribute, the hover event should continue and not end prematurely. - Mozilla Default theme Monitor: Dell P1110 Video Card: nVidia Quadro4 700 XGL w/ Dualview enabled Processor: Intel XEON 1.8 GHz Memory: 1GB OS: Windows 2000 SP3
Updated•21 years ago
|
Whiteboard: DUPEME
Comment 1•21 years ago
|
||
I notice the same problem. Also, hovering over items on the personal toolbar, or child items in any of the application menus (File, Edit, View, etc.) had the same problem on the secondary monitor. Same problem on two systems, both running Mozilla 1.4-final on Windows 2000/SP4. One has a pair of NVidia Riva TNT2 Model 64 (32.Meg) based video cards, and the other has a dual-output NVidia Ti4200 (64.Meg) based card. I've used various versions of recent NVidia drivers. This problem has been around for a long time.
Comment 2•21 years ago
|
||
Either a duplicate of 159277 or 98830, it seems more like 159277. *** This bug has been marked as a duplicate of 159277 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•