Closed
Bug 50562
Opened 25 years ago
Closed 3 years ago
Non-opaque menus don't highlight on mouseover
Categories
(Core :: XUL, defect, P3)
Tracking
()
RESOLVED
INCOMPLETE
Future
People
(Reporter: millennium, Unassigned)
Details
Attachments
(1 file)
|
59.06 KB,
image/jpeg
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (Win95; U)
BuildID: 2000082808
If a user has set the menus to be transparent, the menu items do not highlight
as the mouse passes over them. Note that the menus still *work* just fine; they
just don't highlight properly (which is potentially a usability issue).
Reproducible: Always
Steps to Reproduce:
1) Add the following to your user.css:
<code>menupopup { opacity: <i>x </i>!important; }</code>
where <i>x </i>is any value between 0 and 1 (I suggest 0.9, but any value
works).
2) Start Mozilla and use any menu.
Actual Results: The menu functions, but items do not highlight when the mouse
is passed over them.
Expected Results: Menu items highlight when the mouse passes over them.
Comment 1•25 years ago
|
||
CCing Hixie, said to be "the man" in #mozilla. I've tried adding the snippet
below to both userchrome.css and usercontent.css, in profiledir/chrome/ but it
doesn't change anything.
Gerv
Comment 2•25 years ago
|
||
are you still seeing this with new builds? we need a testcase
Comment 3•25 years ago
|
||
This bug sat here too long, it's a bit obsolete now. To reproduce, create a file
at profiledir/chrome/userchrome.css and put this line it:
menupopup { -moz-opacity: 0.5 !important; }
I'm seeing 2 problems (using recent commercial and mozilla builds on the Mac).
- The first bug is very similar to what is described by the reporter. If you use
a menu at the bottom of a browser window ("Business/Tech/Fun/Interact" in
commercial builds, or just "Mozilla" in public builds), the menu items are not
highlighted correctly. The selection is jerky, it stays on just a fraction of a
second, and it doesn't highlight the text itself but just the margins on both
sides of the menu item.
- The second bug can be seen in the popup menus of the Preferences dialog. Go to
the Font panel and click the Font popup. If you have plenty of fonts and the
dropdown list doesn't fit in the monitor, you will see the entries displayed
twice with a small offset offset (I guess because the list was drawn in 2
passes). Then is you move the mouse over the items, the highlight leaves some
traces. I'm going to attach a screen snapshot.
Reassigned to XP Toolkit / Widgets.
Assignee: pierre → trudelle
Status: UNCONFIRMED → NEW
Component: Style System → XP Toolkit/Widgets
Ever confirmed: true
QA Contact: chrisd → jrgm
Comment 4•25 years ago
|
||
Comment 5•25 years ago
|
||
Note that in the snapshot I attached, the problems only appear at the bottom of
the dropdown list (double display + traces of hilited items).
Comment 6•25 years ago
|
||
->pinkerton/future
Assignee: trudelle → pinkerton
Target Milestone: --- → Future
Comment 7•24 years ago
|
||
wow, i love this screenshot ! translucent menus is a completely useless feature
but i love it, it's fun. i'm voting for it :-)
ps: Win 2K and Mac OS X have some similar feature, btw...
URL: (not applicable)
Umm translusency doesn't seem to work anymore?
Was it just too complicated, or did it regress without anyone noticing?
Comment 9•21 years ago
|
||
Highlighting does work now on Win2k. Anybody on other (Win)OSes like 95 to test?
Translucency does not fully work anymore. The menu fades, but there is no
background visible through them.
I also tried making other elements (like menuitems) translucent, but this
crashed moz.
Comment 10•3 years ago
|
||
Windows 95, eh?
Is this worth trying to reproduce?
Comment 11•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:enndeakin, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: mikepinkerton → nobody
Flags: needinfo?(enndeakin)
Comment 12•3 years ago
|
||
Too old to be relevant.
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(enndeakin)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•