Closed Bug 200857 Opened 20 years ago Closed 10 years ago

personal toolbar BM menu has a separator that the standard toolbar BM menu does not have

Categories

(SeaMonkey :: Bookmarks & History, defect)

defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: deleteduser54318, Unassigned)

Details

(Whiteboard: [2012 Fall Equinox])

Attachments

(1 obsolete file)

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4a) Gecko/20030401

... between "Bookmark This Group of Tabs" and "Manage Bookmarks...". a minor
problem for the redundant personal toolbar bookmarks menu.

Reproducible: Always

Steps to Reproduce:
1. look at the standard toolbar BM menu.
2. look at the personal toolbar BM menu.

Actual Results:  
inconsistency between redundant menus

Expected Results:  
no inconsistency between redundant menus or no redundant menus
Confirming. The personal toolbar bookmarks menu has an additional separator as
described.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This patch removes the extra menu seperator from the bookmarks menu in the
personal toolbar.
Comment on attachment 138343 [details] [diff] [review]
Remove the extra menuseperator in the Personal Toolbar

please review
Attachment #138343 - Flags: review?(p_ch)
Product: Browser → Seamonkey
Henrik, p_ch is no longer doing reviews - patch review needs to be reassigned.
Assignee: bugs → nobody
QA Contact: chrispetersen → bookmarks
Comment on attachment 138343 [details] [diff] [review]
Remove the extra menuseperator in the Personal Toolbar

That file has moved to mozilla/suite/browser/.
Attachment #138343 - Attachment is obsolete: true
Attachment #138343 - Flags: review?(p_ch)
WFM, no extra separator here
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0 SeaMonkey/2.15a1
Build identifier: 20120921003032
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Whiteboard: [2012 Fall Equinox]
You need to log in before you can comment on or make changes to this bug.