Bug 160747 - Clicking weblinks in one viewport drags firefox to that viewport
Summary: Clicking weblinks in one viewport drags firefox to that viewport
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-12 15:10 UTC by w.posche
Modified: 2017-01-07 22:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description w.posche 2008-04-12 15:10:47 UTC 
Version:            (using KDE 4.0.3)
Installed from:    SuSE RPMs
OS:                Linux

I usually have Kontact running on viewport 2 and Firefox on viewport 3. When I click a link in Kontact's Summary view the requested page is opened in a new tab in firefox - good so far. But when the page is opened, Firefox changes viewports: it vanishes on viewport 3 and appears on viewport 2 so I manually have to drag it back to viewport 3. To me, this is a bug so it would be great to change this behavior.
Comment 1 Aaron J. Seigo 2008-06-16 04:37:14 UTC 
i have no idea if this is a kontact issue or a firefox one, but it certainly isn't a plasma issue. i'll let the kontact people decide if it is their bug or not.
Comment 2 Dario Andres 2008-12-21 20:47:56 UTC 
Can you still reproduce this bug with a recent KDE version? (4.1.3 / 4.2beta2 / 4.2svn) ?  Thanks :)
Comment 3 Denis Kurz 2016-09-24 19:21:11 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:31:50 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.