Closed Bug 265291 Opened 20 years ago Closed 20 years ago

Winstripe theme in textmode hides menu button dropmarker in toolbar.

Categories

(Firefox :: Toolbars and Customization, defect)

x86
Windows ME
defect
Not set
minor

Tracking

()

RESOLVED INVALID

People

(Reporter: mromarkhan, Assigned: bugs)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.7.3) Gecko/20041014 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.7.3) Gecko/20041014 Firefox/0.10.1

Not sure if this is a duplicate of 
Bug 216266,
or depends on it, or if it is fixed, 
but here goes.

Possible code in question (browser.css)
845 toolbarbutton.chevron > .toolbarbutton-menu-dropmarker {
846   display: none;
847 }


From the text identity team (me, as for now):
In text mode
1) users cannot go forward or backwards in history
since the dropmarker is hidden.
2) When the bookmark toolbar is overflowed a little dropmarker arrow
appears in image mode. In text mode, no arrow appears.  Minor,
since can click placeholder.

Hacks

/*For 1*/
toolbar[mode="text"] .toolbarbutton-menubutton-dropmarker 
{
	display: -moz-box !important;
}
/*For 2*/
toolbar[mode="text"] toolbarbutton.chevron > .toolbarbutton-menu-dropmarker 
{
	display: -moz-box !important;
}

Reproducible: Always
Steps to Reproduce:
1. Right Click Toolbar, Customize
2. Click Show: Text
Actual Results:  
No drop marker for back, forward,  
and over-flowed bookmark toolbar

Expected Results:  
Show me some arrows.
WFM on Mozilla/5.0 (Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041023 Firefox/1.0

Please try a current build.
Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.7.3) Gecko/20041024 Firefox/1.0

Okay got the nightly,
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2004-10-24-06-0.9/firefox-1.0.en-US.win32.zip

Works great!

Thanks Simon 'sipaq' Paquet  
for informing me on this
change.

Have a good day.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
QA Contact: bugzilla → toolbars
You need to log in before you can comment on or make changes to this bug.