Closed Bug 135971 Opened 23 years ago Closed 23 years ago

strip comment field on Mozilla/Netscape Shortcut icon files on Windows

Categories

(SeaMonkey :: Installer, defect)

x86
Windows 2000
defect
Not set
trivial

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 42604

People

(Reporter: mozbugz, Assigned: dveditz)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+)
Gecko/20020405
BuildID:    2002-04-05-03

In windows: this is the shortcut files that are placed on the desktop.  shows
two tooltip lines.. were we should only have Mozilla xxx we have 2 copies of
this on the tooltip text and makes us look bad..







Reproducible: Always
Steps to Reproduce:
1.If you go hover over mozilla's shortcut file it shows the tooltip as:



Actual Results:  you see two lines in the tooltip text.

Mozilla  or   Netscape xxx
Mozilla       Netscape xxx


Expected Results:  where as other apps show just 1 line for the tooltip; it
should come up as:

Mozilla  or   Netscape xxx


Open properties of the icon shortcut.  There is a comment field where we write
in Mozilla, or netscape x.x.x.  See screenshot 1 for why we get a double
tooltip.  And screenshot two for how this can be fixed.  

We need to strip the comment field information from the icon files, as this
tooltip information is already generated by the shortcut app name.. no the
filename I believe.
not sure where to find the file that creates this or how to fix it.. but once
its on the desktop a user can easily fix it.  This appears to be installer based.  
Keywords: mozilla1.0, nsbeta1
oh yeah, this is fine with desktop shortcut files.. we dont need to strip it,
but it is the quick launch bar where we place the shortcut which has the
problem.. although doing this for the desktop icons I dont think would hurt us here.
dupe

*** This bug has been marked as a duplicate of 42604 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.