Version: unknown (using KDE 3.1.1) Installed from: SuSE Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB When you click on a link which is supposed to open a new window (mmb, context menu 'Open in new window' or a <a> link with '_new' target) and the mime type of the link's content is handled by an external viewer, two windows will be opened. Only the external viewer should open. Example: configure file associations to open text/plain in KWrite. Then mmb-click on a link that leads to a text/plain. Two windows open, one is KWrite the other is an empty Konqueror instance. Only KWrite should open.
Seconded
I agree that this is not nice behavior and should be fixed. It is still present in 4.0.
I am unable to reproduce this in Konqueror 3.5.9. Any text file that I mmb-click after setting kwrite as standard text editor opens the text in a tab in konqueror's embedded text reader.
That's another bug, I think: sometimes the embedded kpart opens even if external viewer is the default, if the link opens in a new window.
I can confirm this bug for 3.5.9 and trunk r803905. I can also confirm what's mentioned in c#4: Some mimetypes are open in an embedded viewer in a new windows (eg. pdf for me), while others open an empty konqueror window and the external application. mmb-clicking on a mailto-link does that as well.
This is still present in konqueror 4 svn trunk 828814, but I think it is not a bug, let me explain: W3C HTML 4 says at http://www.w3.org/TR/REC-html40/present/frames.html#adef-target If any target attribute refers to an unknown frame F, the user agent should create a new window and frame, assign the name F to the frame, and load the resource designated by the element in the new frame. This is what konqueror does. Then, if the content needs an external viewer, konqui spawns an external viewer. This happens also to Firefox 3 and Opera 5.91.
Message from the Bugsquad and Konqueror teams: This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore. If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report. Thank you for your understanding.