Pinned url's in the Seamonkey taskbar does not work if pinned by dragging a url icon from the desktop



8 months ago
8 months ago


(Reporter: Peter Madsen, Unassigned)



SeaMonkey 2.46 Branch
Windows 7

Firefox Tracking Flags

(Not tracked)




8 months ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
Build ID: 20161213183751

Steps to reproduce:

1. I drag the web site icon in Seamonkeys address bar to the desktop to make an Internet shortcut.
2. I then Drag this icon over Seamonkeys icon on the taskbar, where I am prompted to pin it to Seamonkey.
3. Right-cliking Seamonkey icon in the taskbar, now show the pinned Interne shortcut in the list of pinned sites, as expected.
4. I click the new site...

Actual results:

I get a message with this text in Danish:
[Window Title]
Der er et problem med genvejen

Denne internetgenvej kan ikke åbnes. Protokollen “SeaMonkeyURL” har ikke et registreret program.


Translated it is something like:
[Window Title]
There is a problem with the shortcut

This Internet shortcut can not be opened. The Protocol “SeaMonkeyURL” does not have an registered program.


Here is my Registry setting for SeamonkeyURL:
@="SeaMonkey URL"
"FriendlyTypeName"="SeaMonkey URL"

@="C:\\Program Files (x86)\\SeaMonkey\\seamonkey.exe,0"



@="\"C:\\Program Files (x86)\\SeaMonkey\\seamonkey.exe\" -requestPending -osint -url \"%1\""




Expected results:

Seamonkey should have opened the pinned shortcut.

I can add that the same procedure works in FireFox, Opera and Internet Explorer 11, but not in Google Chrome and Safari

Comment 1

8 months ago
I can confirm reporter's observations with unzipped installer of  UNofficial (by Adrian Kalla) en-US SeaMonkey 2.53a1 (NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0 Build 20170620091523  (Default Classic Theme) on German WIN7 64bit.

but I don't know what that means. SM-problem? OS-Problme? Something else?
Keywords: reproducible
OS: Unspecified → Windows 7

Comment 2

8 months ago
I can now add that it is only on my Windows 7 PC's that it happens, not on my Windows 8.1 and 10 machines.
You need to log in before you can comment on or make changes to this bug.