1318596 - When click link which should open link target in new TAB (due to Preferences) target wrongly opens in new Window

Status: RESOLVED DUPLICATE of bug 1316104

(SeaMonkey :: Tabbed Browser, defect)

Description

[Stefan Haas]

Attachment: notab.gif

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49a1
Build ID: 20161110004327

Steps to reproduce:

Clink on HTML link in web page


Actual results:

New window pops up (and no way to change link behavior preferences)


Expected results:

New tab in current window (default behavior since long, and possibility to change this in preferences)

Comment 1

[Rainer Bielefeld]

I think this one is INVALID. 

@reporter
Preference you want to change is in ˋEdit → Preferences → Browser → Link Behaviorˊ, but not in "Tabbed Browsing".

@Reporter: Please feel free to reopen this Bug if you still can reproduce the problem with a current SeaMonkey Trunk version  and if you can contribute a CORRECT step by step instruction how other users can reproduce the problem reliably due to <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines>  (containing every key press and every mouse click).

Comment 2

[Stefan Haas]

Thanks for the info - then the tabbed browsing is definitely BROKEN.

All configs indicate diversion into tabs, but only when I do it explicitely a new tab is created. All others create new windows.

Comment 3

[Stefan Haas]

Attachment: link.gif

According to this config (not changed) I should see lots of tabs instead of lots of windows.

Comment 4

[Rainer Bielefeld]

NOT reproducible with server installation of official en-US SeaMonkey 2.49a1  (NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0 Build 20161107002359  (Default Classic Theme) on German WIN7 64bit and preferences due to reporter's attachment 2016 [details]-11-18 17:14 CET: 

1. Proceeding as per Bug 1316104 comment #12 click on „48 gefixte“ -
   SM tries to open in new TAB as expected (but crashes)

I will try WIN10 later.


@reporter:
To be honest: I still haven't a clue what your problem might be. And also not what you expect for whatever kind of link. Please avoid meaningless phrases like "is broken", "does not work", but contribute a clear step by step instruction containing every key press and every mouse click how to reproduce your problem due to <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines> (similar to report in Bug 1139273)
I think it's crystal clear that we at least need information concerning the hyperlink with which you observe unexpected behavior.
What is your result proceeding test in step 1 above?

Comment 5

[Rainer Bielefeld]

NOT reproducible with server installation of official en-US SeaMonkey 2.49a1  (NT 6.1;  WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Build 20161111004200  (Default Classic Theme) on German WIN7 64bit

REPRODUCIBLE with unzipped official en-US SeaMonkey 2.49a1  (NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Build 20161111004200  (Default Classic Theme) on German WIN7 64bit

I will do my own tests to find out whether
a) Related to WIN 10?                                                        or
b) New behavior after Build 20161107002359?                                  or
c) other reasons?

Comment 6

[Rainer Bielefeld]

Error in second User Agent String in comment above: should be "... German _WIN10_ 64bit"

a): seems WIN10 related, because
b): also  NOT reproducible with unzipped official en-US SeaMonkey 2.49a1  (NT 6.1;
    WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Build 20161111004200  
   (Default Classic Theme) on German WIN7 64bit: this version from same source.zip
    as I used for my tests on WIN10 still CRASHes on WIN7

@FRG: I wonder whether these observations might have impact at Bug 1316104?

Comment 7

[Frank-Rainer Grahl (:frg)]

>> @FRG: I wonder whether these observations might have impact at Bug 1316104?

I sent you a link to a (hopefully) fixed 2.49a2. Maybe you can try this one. Possibly happens because I bungled the first patch for bug 1316104 which is in current 2.49a2 and 2.50a1.

Comment 8

[Frank-Rainer Grahl (:frg)]

Works fine for me using the fixed 2.49a2 in Win10. 

https://seamonkeyde.wordpress.com/ Link under '48 gefixte AOO – Bugs' opens a new tab and no crash.

Comment 9

[Rainer Bielefeld]

Was ok with German SeaMonkey 2.46 (Windows NT 10.0; WOW64; rv:49.0)  Gecko/20100101 Firefox/49.0 Build 20161010215124  (Default Classic Theme)  on German WIN10 64bit

@ Frank-Rainer Grahl
I will test your build with patch, soon

Comment 10

[Rainer Bielefeld]

(In reply to Frank-Rainer Grahl from comment #8)
> Works fine for me using the fixed 2.49a2 in Win10. 

Yes, your unofficial (by FRG) en-US SeaMonkey 2.49a2 Build 20161118170316 does no longer show the problem for me, so this one can be marked as FIXED when the FIX for Bug 1316104 will have been pushed.