Closed
Bug 207779
Opened 22 years ago
Closed 22 years ago
Bookmark Manager View->Show Columns menu does nothing.
Categories
(SeaMonkey :: Bookmarks & History, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: alther, Assigned: jblanco)
References
Details
(Keywords: fixed1.4.1)
Attachments
(1 file, 3 obsolete files)
|
3.27 KB,
patch
|
janv
:
review+
bryner
:
superreview+
mkaply
:
approval1.4.1+
mkaply
:
approval1.5b+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529
Open the Bookmark Manager. Use the View->Show Columns menu to show/hide columns
to view. Checking/unchecking columns from the menu has no affect at all. The
menu is initialized correctly (i.e. the visible columns are correctly checked),
but it doesn't look like the code is hooked up when checking/unchecking columns.
Also, you can not uncheck the Name column from the menu either even though it is
enabled. Since you can not hide the Name column, this menu option should be
shown in a disabled state. The container control button for selecting columns
correctly disables the Name column.
If you show/hide columns using the button on the container control, it works fine.
Reproducible: Always
Steps to Reproduce:
1. Open the Bookmark Manager
2. View->Show Columns menu. Notice this submenu is correctly initialized.
3. check/uncheck various columns. Notice this action has no effect on the
columns visible in the container. Also note that you can never uncheck the Name
column even though the menu option is enabled.
4. Use the container control column select button. Checking/unchecking columns
correctly changes the column visibility. Also note that the Name column is
disabled properly giving the user feedback that they can not change the
visibility of the Name column.
Actual Results:
The columns never show/hide as needed.
Expected Results:
That the columns show/hide as appropriate. I also expect the Name menu option
be disabled since you can never hide that column.
Comment 1•22 years ago
|
||
Confirming issue in the 2003-06-02-08 Macho and Win32 trunk builds.
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 2•22 years ago
|
||
This also happens on OS/2 - mozilla 1.4 release build
OS: Windows 2000 → All
| Assignee | ||
Comment 3•22 years ago
|
||
bookmarksManager.js is using the resource attribute from the columns to
show/hide them. This attribute was set in bookmarksTree.xml and each column
had a "sort" attribute, but this was removed when the patch for bug 205378 got
checked in (big bookmarks change). In this patch I set the Name option in the
menu to be disabled and added the sort attribute for each column back into
bookmarksTree.xml because it's still used to show/hide columns. Why was the
sort attribute removed?
| Assignee | ||
Comment 4•22 years ago
|
||
OK, adding the sort attribute back in does affect the sorting of bookmarks.
Instead of adding the "resource" attribute back into bookmarksTree.xml, I
removed it from bookmarksManager.js. I'm now using the label attribute to
show/hide columns, added the "id" attribute to use instead of resource/"sort"
because that was removed and no longer used, and actually checking for Name and
disabling it in the Show Columns menu.
Attachment #127952 -
Attachment is obsolete: true
Updated•22 years ago
|
Attachment #127960 -
Flags: review?(varga)
Comment 5•22 years ago
|
||
The last patch looks good, although it can be improved a bit
1.
I'm worried that now you end up with 2 elements sharing the same id.
So it would be probably better to use other attribute on the menuitems, e.g. "ref"
2.
I think, toggleColumnVisibility() can now take the id attribute instead of
resource/label
Let me know if there are any issues with that.
Assignee: chanial → jblanco
Comment 6•22 years ago
|
||
I found out that these tree column ids are actually anonymous, anyway it would
be better to use "ref" attribute on menuitems.
| Assignee | ||
Comment 7•22 years ago
|
||
Jan, did you mean change the id to ref here -
- menuitem.setAttribute("id", "columnMenuItem:" + columns[i].resource);
+ menuitem.setAttribute("id", "columnMenuItem:" + columns[i].id);
where the "id" would now be "ref" because menuitems already have a given id?
or did you mean change it here -
+ id: child.getAttribute("id"),
and use a "ref" for the id instead?
I'll update toggleColumnVisibility() to take the id attribute.
Comment 8•22 years ago
|
||
I meant:
- menuitem.setAttribute("id", "columnMenuItem:" + columns[i].resource);
+ menuitem.setAttribute("ref", "columnMenuItem:" + columns[i].id);
...
- var resource = aEvent.target.getAttribute("resource");
- if (resource != "") {
+ var ref = aEvent.target.getAttribute("ref");
+ if (ref != "") {
var bookmarksView = document.getElementById("bookmarks-view");
- bookmarksView.toggleColumnVisibility(resource);
+ bookmarksView.toggleColumnVisibility(ref);
| Assignee | ||
Comment 9•22 years ago
|
||
Thanks Jan. I used "ref" instead of "id" for the menuitem attribute, but I
kept the use of label instead of ref in toggleColumnVisibility() because
"columnMenuItem:" gets in the way. When I remove the columnMenuItem string
from the id, the checkmarks do not show in the right places.
Attachment #127960 -
Attachment is obsolete: true
| Assignee | ||
Comment 10•22 years ago
|
||
Attachment #128037 -
Attachment is obsolete: true
Comment 11•22 years ago
|
||
Comment on attachment 128180 [details] [diff] [review]
more up to date patch
r=varga
Attachment #128180 -
Flags: review+
Updated•22 years ago
|
Attachment #128180 -
Flags: superreview?(bryner)
Updated•22 years ago
|
Attachment #127960 -
Flags: review?(varga)
Updated•22 years ago
|
Attachment #128180 -
Flags: superreview?(bryner) → superreview+
Comment 12•22 years ago
|
||
Comment on attachment 128180 [details] [diff] [review]
more up to date patch
a=mkaply
Attachment #128180 -
Flags: approval1.5b+
Attachment #128180 -
Flags: approval1.4.x+
Comment 13•22 years ago
|
||
Fix checked in to branch and trunk
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•22 years ago
|
Keywords: fixed1.4.1
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•