Closed Bug 121556 Opened 23 years ago Closed 14 years ago

2 widgets are created for the URL Bar icon

Categories

(SeaMonkey :: Location Bar, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: pierre, Unassigned)

Details

We create two widgets for the URL bar icon (the LINK REL="icon" thingy).  They 
are both at location (15, 273) on a Modern skin.  One is 16px by 16px but the 
other one has an empty rect.  Besides the fact that a widget with an empty rect 
is pretty useless, this one also seems to be always invisible.  Could we remove 
it?

I detected this problem when working on how updates are handled on the Mac.  See 
bug 69010 comment #70 and attachment #62520 [details] for more info.
Well, one is the normal page proxy icon and the other is the favicon.  They are
both used.  We could merge them, but that would make things more difficult -
what is this costing us?
Amongst the seven native widgets that we still have to display a basic web page, 
two are for this single icon and one seems to be always unused.  I have no idea 
how much it costs us on the different platforms but not much, I guess (the page 
load tests will probably not show anything on Windows because of the paint 
suppression timer).  I just know that we backed off from using native widgets for 
everything 2 years ago because it was too expensive so when I see one which is 
never used, I file a bug :-)
Status: NEW → ASSIGNED
Target Milestone: --- → Future
This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".
OS: Mac System 9.x → MacOS X
Not worth fixing.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
It might be worth fixing for other platforms.  (This is probably All/All, I'd
think.)
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Product: Core → SeaMonkey
Assignee: hewitt → nobody
Status: REOPENED → NEW
QA Contact: claudius → location-bar
Target Milestone: Future → ---
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
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: 21 years ago14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.