Bug 290020 - opening external link in new tab BUT on current desktop
Summary: opening external link in new tab BUT on current desktop
Status: RESOLVED DUPLICATE of bug 237732
Alias: None
Product: rekonq
Classification: Applications
Component: general (show other bugs)
Version: 0.8.0
Platform: unspecified Linux
: NOR minor
Target Milestone: 0.9
Assignee: Andrea Diamantini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-28 16:13 UTC by Diggory Hardy
Modified: 2012-01-25 22:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Diggory Hardy 2011-12-28 16:13:32 UTC
Version:           0.8.0 (using KDE 4.7.2) 
OS:                Linux

I use multiple desktops/workspaces and like it if when I open a link it shows up on my current desktop, but in an existing browser if one's there. Several browsers (including konqueror but not chromium) seem to do this as expected.

Currently I can either set rekonq to open links in new tabs (opens in a window on a different desktop if there is no window on the current desktop but one elsewhere), or to never open external links in a new tab.

Reproducible: Always

Steps to Reproduce:
(irrelevent)


Expected Results:  
Opening an external link with rekonq set to the default browser should open a tab in an existing window _on the current desktop_ if there is one, otherwise open a new window.
Comment 1 Andrea Diamantini 2011-12-29 07:49:54 UTC
In 0.9 you'll have the option to open external links in new windows instead of in tabs, so that links will always open in the same desktop you are using.
This should be the same konqueror behaviour. Is this enough?
Comment 2 Diggory Hardy 2011-12-29 16:54:42 UTC
If it automatically choses between new tab and new window depending on what's available on the current desktop. IIRC konqueror doesn't explicitly advertise this functionality but does do it.
Cheers,
Comment 3 Andrea Diamantini 2012-01-25 22:14:11 UTC

*** This bug has been marked as a duplicate of bug 237732 ***