All users were logged out of Bugzilla on October 13th, 2018
* MailNews uses the Column Picker widget to select columns to display. * The Bookmark Manager has both View|Show Columns and column picker. * The History Manager has both View|Show Columns and column picker.
using build 2001041214 -MailNews uses the Column Picker widget to select columns to display. -Bookmark Manager has both View|Show Columns and column picker (see also bugs #75825 and #71776 ) -Search Bookmarks/History _only_ has View|Show Columns. What is the rationale behind this seemingly inconsistent UI design?
partly due to the fact that outliner and trees support different column manipulations, I think....
Will this get fixed once we move to one system?
Status: UNCONFIRMED → NEW
Ever confirmed: true
CCing Ben, who is rewriting bits of bookmarks. Gerv
Assignee: mpt → blaker
Component: User Interface Design → XP Apps: GUI Features
QA Contact: zach → paw
At least on Windows "Search bookmarks" also has both ways to choose the columns to be displayed. This bug is filed on Linux, but I doubt that there is no column picker widget, is there? If not, the only inconsistency left is that there is only one way to choose from the columns in the Mail window, which doesn't seem much of a problem to me... anyone disagree? Reinout, what about you?
Reassigning obsolete bugs to their respective Seamonkey owners (i.e. nobody). If you want this fixed for Firefox, change the Product and Component accordingly and reassign back to me.
Assignee: firefox → guifeatures
Filter "spam" on "guifeatures-nobody-20080610".
Assignee: guifeatures → nobody
QA Contact: pawyskoczka → guifeatures
Is this still relevant today? Are you sure 'jag' is working on this?
The first two items are still valid. Though I doubt jag is working on it.
Assignee: jag-mozilla → nobody
OS: Linux → All
Hardware: x86 → All
User Story: (updated)
Summary: Arbitrary use of View|Show Columns and column picker → Inconsistent use of View|Show Columns and the column picker widget to select columns to be shown.
You need to log in before you can comment on or make changes to this bug.