Closed
Bug 143859
Opened 23 years ago
Closed 15 years ago
No Way to Leave Disable Favicon from tabs
Categories
(SeaMonkey :: Tabbed Browser, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: sailfish, Unassigned)
References
(Blocks 1 open bug)
Details
There appears to be no way to disable favicons from displaying on tabs without
disabling them globally. I'm creating a skin which replaces the normal
bookmark-item icon with a stylized image for the tab end. This works well until
a tab is opened for a site employing favicons like, say, mozilla.org.
There should be a way to disable the favicon for the tabbrowser section. For
example:
.tabbrowser-tab-favicon {
display: none
}
Of course, this should have no effect on the bookmark-item icon ... just any
favicon that may come along.
Comment 1•23 years ago
|
||
tab > .tab-icon works for me, could you try that?
Reporter | ||
Comment 2•23 years ago
|
||
Christian, that disables all icons on tabs, including the default bookmark-item
and the tab[busy] ones. I'm using those items to provide a custom stylized tab
cap which works wonderfully until a favicon comes on the scene.
I can resolve this by using:
#page-proxy-favicon {
display: none;
}
but that also removes it from the urlbar which I don't want to happen. My
expectation is that one should be able to specifically disable/enable the
showing of the favicon wherever it appears.
Comment 3•23 years ago
|
||
Is this a duplicate of 109899(option to disable Tab icons)?
Reporter | ||
Comment 4•23 years ago
|
||
Robert, not really. I already can disable tab icons but I'm using them to create
a specialized left-side tab contour, i.e., I've replaced the default
"list-style-image:
url("chrome://communicator/skin/bookmarks/bookmark-item.gif");" reference in
browser.css with my own image. However, whenever a favicon-enabled site is
tabbed, it trashes my kewl tab-cap.
Reporter | ||
Comment 6•23 years ago
|
||
timeless, yes but, sadly, not for this :-)
ok, well then enough of this, the problem is probably that tabbed browser does
direct sets instead of css rules.
Assignee: ben → jaggernaut
Status: UNCONFIRMED → NEW
Component: Skinability → Tabbed Browser
Ever confirmed: true
QA Contact: pmac → sairuh
Reporter | ||
Comment 8•23 years ago
|
||
timeless, in purusing the skin/content/*.jar xml & xul files it appears that it
only checks to see if the globally-defined favicon support is enabled and, if
so, it processes the url (including any site-enabled favicons), i.e., it doesn't
appear there are provisions for nodal favicon enabling???
I say this without a lot of certainty since that code is quite convuluted and
I've misplaced my XML/XUL decoder ring :-(
Updated•22 years ago
|
QA Contact: sairuh → pmac
Assignee | ||
Updated•16 years ago
|
Product: Core → SeaMonkey
Updated•16 years ago
|
Assignee: jag → nobody
QA Contact: pmac → tabbed-browser
Comment 9•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 10•15 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: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•