Closed Bug 109899 Opened 24 years ago Closed 16 years ago

option to disable Tab icons

Categories

(SeaMonkey :: Tabbed Browser, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bugZ, Unassigned)

References

Details

(Whiteboard: WONTFIXME)

build 2001111303 IMO, something was overlooked with site icons in bug 32087 and bug 108823. When they are disabled in prefs, the default bookmark icon displays in all tabs. Since they are all the same icon, they really serve no purpose in Tabs other than taking up space that could be used to show a little more of the page title. Eliminating the Tab icon would be particularly beneficial with smaller window sizes, or with a sufficient number of open tabs. There should be a Tab pref to disable the icons altogether.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
Shouldn't the bookmark icons in the tabs be available to drag around? Why should you have to switch to the tab and use the URL Bar's icon to, for example, add a bookmark to the personal toolbar? If this isn't the case, the original poster has a point. (And it looks like this isn't implemented right now, if it's even planned at all.)
Reassigning to new component owner.
Assignee: hyatt → jaggernaut
Status: ASSIGNED → NEW
QA Contact: blaker → sairuh
Give me words instead of icons any day. All these icons do is waste screen estate. Please change OS and platform to all. I would vote all available votes if only it would let me. The directions on the voting page seem to indicate a number can be substituted for a checkmark, but 2002040708 for OS/2 won't let me.
*** Bug 153673 has been marked as a duplicate of this bug. ***
Changing OS and Plataform to All due to mrmazda request, and also changing severity to enhancement.
Severity: normal → enhancement
OS: Windows 98 → All
Hardware: PC → All
> Shouldn't the bookmark icons in the tabs be available to drag around? That's bug 111905. > Since they are all the same icon, they really serve no > purpose in Tabs other than taking up space While I agree for the most part, it should be pointed out that, at the very least, I would NOT like to lose the animated icon displayed when a site is loading. > The directions on the voting page seem to indicate a > number can be substituted for a checkmark Bug 90175 - the voting text is misleading / incorrect.
I don't think getting rid of the useless icons and keeping the loading indicators are mutually exclusive concepts. Let the loading icon pop in when needed and exit when done. Personally I don't find either useful. Maximizing the tab text is my pref.
I agree - I just wanted to point out that the icons do do something (at times) other than simply sit there uselessly. At the moment (at least until bug 111905 is fixed) I would personally rather see the icons only when a tab is loading, then have them disappear altogether. But based on people who don't even want to see tab loading icons - do we need more than a Yes / No (based on site icons) pref for this? (My answer to this is no, but I felt the question should be asked.)
QA Contact: sairuh → pmac
retargeting
Target Milestone: mozilla1.1alpha → Future
http://www.mozilla.org/unix/customizing.html Select the rules you want, follow the directions and use them. note that most css rules (e.g. these) are not platform specific.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
At best that link is a workaround. It certainly doesn't introduce any UI option to the normal end user of this program.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Reassigning to default owner (I believe it should now be a generic email account).
Assignee: jag → tabbed-browser
Status: REOPENED → NEW
Whiteboard: WONTFIXME
Product: Core → SeaMonkey
Assignee: tabbed-browser → nobody
QA Contact: pmac → tabbed-browser
Target Milestone: Future → ---
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
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
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
Group: core-security
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
Group: core-security
A UI based option for another small UI change would be overkill. WONTFIX
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago16 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.