1398497 - Link behavior pref for other applications ignored, always opens new window

Status: RESOLVED DUPLICATE of bug 1379369

(SeaMonkey :: Preferences, defect)

Description

[K Chayka]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 SeaMonkey/2.54a1
Build ID: 20170908062737

Steps to reproduce:

This has been happening for some weeks, both Win32 and Win64 builds.

1. Open a browser window (content of the window is irrelevant, e.g. about:blank works as well as any other page) 
2. Prefs → Browser → Link Behavior → Links from other apps: A new tab in the current window
3. Open any 3rd party document containing a clickable link, e.g. a pdf, MS-office doc, Open/Libre Office doc, etc.
4. Click on the 3rd party link


Actual results:

A new browser window opens showing the home page defined in prefs. The link from the 3rd party doc is not displayed.


Expected results:

A new tab in the existing window should open, showing the 3rd party link.

This incorrect behavior also occurs when the pref is set to The current tab/window rather than a new tab - a new window opens showing the home page.

Note if no browser window is open (Seamonkey not running, or only a mail-news window is open), then a browser window opens and shows the 3rd party link.

Comment 1

[K Chayka]

Attachment: screen shot of error console after clicking on 3rd party link

Comment 2

[Rainer Bielefeld]

This one probably is a DUP of "Bug 1380566 - Click on web link opens predefined Home page instead of link target", which itself is a DUP of "Bug 1379369 - Port Bug 1364016 [Have _openURIInNewTab() provide the correct triggeringPrincipal] to SeaMonkey"

Bug 1379369 has become fixed 2017-09-10 22:00:09 CEST

@reporter:
Can you please test a very latest trunk build and leave a comment here and in "Bug 1379369"?

Comment 3

[Frank-Rainer Grahl (:frg)]

Yes this should be fixed with bug 1379369.

There are still 2 startup problems in 2.54. Bug 1394101 and Bug 1392929 might need to be fixed too for this to be effective.

Comment 4

[K Chayka]

Build identifier: 20170911061039

Still broken. Will attach screenshot of error console.

Comment 5

[K Chayka]

Attachment: screen shot of error console on Build identifier: 20170911061039

Comment 6

[Frank-Rainer Grahl (:frg)]

per email.