Closed
Bug 196228
Opened 23 years ago
Closed 22 years ago
Button rollovers work like a charm in IE and not at all in Mozilla
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Christian.Blackburn, Assigned: asa)
References
()
Details
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
While browsing the Nvidia website in MSIE the toolbar buttons are right next to
each other along the same vertical plane. However in Mozilla they're spaced out
at an inconsistant interval and have unequals top values.
Reproducible: Always
Steps to Reproduce:
(On Windows 2000 SP3)
1. Start Mozilla 1.21
2. Paste the following URL into the address bar:
http://www.nvidia.com/view.asp?IO=winxp-2k_41.09
3. Press Enter
4. Move your mouse over all the buttons once
Actual Results:
After Step#3:
The page loads with the buttons spaced out far apart across the horizontal
plane. The top position of the buttons also varies.
After Step#4:
The buttons move more inline with where they are supposed to be. However the
Expected Results:
After Step#3:
The buttons should have loaded right next to each other along the horizontal
plane.
After Step#4
While the buttons do move closer together you'll notice that the Home and
Download buttons are still lower than they should be. Those two buttons should
be in line with the rest of them running across the top of the browser's display
window.
| Reporter | ||
Comment 1•23 years ago
|
||
| Reporter | ||
Comment 2•23 years ago
|
||
| Reporter | ||
Comment 3•23 years ago
|
||
Comment 4•23 years ago
|
||
*** Bug 196229 has been marked as a duplicate of this bug. ***
Comment 5•23 years ago
|
||
Christian: thank you for such a thorough report!
Reassigning to Browser-General until we can get further information.
This is not likely to be a bug in the JavaScript Engine.
Christian: I notice your build is rv:1.2.1, Gecko/20021130.
Would it be possible for you to get the latest trunk build?
I'm not seeing the bug with my trunk build: 2003022808 on WinNT.
When I do Help > About Mozilla, here is my version:
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4a) Gecko/20030228
Assignee: rogerl → asa
Component: JavaScript Engine → Browser-General
QA Contact: pschwartau → asa
Comment 6•23 years ago
|
||
Also compare bug 193339, "Can't select an option on the menu of nvidia page,
the problem of the position is now fixed, but a new bug as appeared"
Comment 7•23 years ago
|
||
Netscape != Mozilla ;)
Summary: Button rollovers work like a charm in IE and not at all in Netscape → Button rollovers work like a charm in IE and not at all in Mozilla
Comment 8•23 years ago
|
||
WFM too - 8 hours old (need to make a new one !) CVS based build, WinXP-Sp1.
But I am facing bug 193339 too.
The good point is that menu is visible and well set-up :-)
Comment 9•23 years ago
|
||
worksforme moz 2003030408/win98
Comment 10•22 years ago
|
||
This WFM on the 20030908 trunk build. Christian, do you still see this behavior
on a recent build (and if necessary, a clean profile)? To me it looks like
nvidia has either cleaned up their site, or the problem was fixed in another
Mozilla bug. If you do not see the problem, please resolve as WORKSFORME. Thanks.
| Reporter | ||
Comment 11•22 years ago
|
||
Hi Guys,
Although I'm also unsure about the cause of the website working in Mozilla:
A. Mozilla has been improved
B. The website's code has been improved
but whatever the cause this bug is outta here.
Cheers,
Christian
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 12•22 years ago
|
||
A bug is FIXED only if there's a patch specifically checked-in for it. The res.
is worksforme.
Severity: major → normal
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Comment 13•22 years ago
|
||
resolving
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•