Closed
Bug 133901
Opened 23 years ago
Closed 14 years ago
Highlighted folder fades away in "Customize Sidebar"(Classic Theme)
Categories
(SeaMonkey :: Themes, defect)
SeaMonkey
Themes
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: gashu, Unassigned)
References
()
Details
Highlighted folder fades away in "Customize Sidebar" of Classic Theme.
I confirmed this on 0.9.9+/2002032708 and 0.9.9.
For customize.css points these two icons though there's neither.
bookmark-folder-closed-sel.gif
bookmark-folder-open-sel.gif
In chrome://communicator/skin/sidebar/customize.css , The codes below are
unnecessarry.
treeitem[selected="true"] > treerow > .treecell-panel[haslink="true"],
treeitem[selected="true"][container="true"] > treerow > .treecell-panel
{
list-style-image:
url("chrome://communicator/skin/bookmarks/bookmark-folder-closed-sel.gif");
}
treeitem[selected="true"][container="true"][open="true"] > treerow > .treecell-panel
{
list-style-image:
url("chrome://communicator/skin/bookmarks/bookmark-folder-open-sel.gif");
}
Assignee | ||
Updated•16 years ago
|
Product: Core → SeaMonkey
Updated•16 years ago
|
Assignee: hewitt → nobody
QA Contact: pmac → themes
Comment 2•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 3•14 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•