You know what is commonly known as "tabbed browsing"? :-) 

I'll state: no. :-) OK now I realize I can right-click and open a link in a Konqueror tab. Cool. Sorry for the badly worded bug report.  However, I agree with you that this should still be added as a new bug because this new KDE3.1 version of Konqueror properly renders more HTML than the previous version. When you are building a site that works correctly for 4 or more browsers there are always cases where the only way you can determine if a browser works or not is through the User Agent.  Though it may be possible to use some JavaScript to determine different Konqueror versions through some undocumented idiosyncracy I do not believe we should leave this research up to each and every JavaScript developer when the User Agent should already contain this information.  

Shouldn't this be part of RELEASE-CHECKLIST? 

I have very mixed feelings about sites checking browser capabilities by 
using user agent string. Fact is that Konqueror is not MS IE, and many 
sites test for MS IE and refuse to run with anything else, and this really 
pisses me off.  
 
IMHO it would be better for the user to upgrade when they find sites that 
don't render properly in older versions instead of websites trying to work 
around it. what if we release a konqueror 3.0.5 version that contains the 
bugfix for the bug that destroys your website.  
 
sorry, but testing for bugs by using the user agent string is broken.  

Perhaps forcing people to upgrade is an option, but I think this is only realistic in the  long term (perhaps 2 years or so). Please consider:    1. People refusing to run with Konqueror because of its User Agent will still refuse to  run Konqueror regardless if the User Agent is Konqueror/3 or Konqueror/3.1. (This  pisses me off too - my bank even does this)    2. I do not believe everyone will upgrade to Konqueror overnight. I'm still running  Mandrake 8.0 at work and have put off upgrading because it (kde/konqueror/etc) works perfectly well for me. It's hard for me to lose a day to upgrade, so I will procrastinate.  Further, if I - or any web developer - does not believe the majority of Konqueror users are using KDE 3.1 then people will continue detecting Konqueror in the User Agent and will either a) continue blocking the browser as older Konqueror browsers do not render this or that HTML/CSS, b) continue degrading the dynamically generated HTML/CSS output to Konqueror so it is compatible with older Konqueror versions.  Another thing, since Konqueror does not display error messages when there are JavaScript bugs sites seem to be saying, "screw it, it's not worth the hassle to support". Sorry, that may have been off topic.  I've noticed the new Konqueror (in KDE 3.1rc2) is so good that I can set my _ie6 variable to true and forget about it. It is ironic, but I think your intention of _not_ testing for bugs by using the User Agent string will come about instantly if you _do_ change the User Agent string to Konqueror 3.1 so developers can assume it is nearly perfectly IE compatible and forget about it.   :-)  

<p> 
Arg. The formatting is off because I didn't realize this was an HTML Comments box. 
</p> 
<p> 
Perhaps the name should be changed from "Additional Comments:" to<br> 
"Additional HTML Comments:" 
<p/> 
Cheers. 
 

<offtopic> 
Er, the HTML comments didn't work. I'm using KDE3.1rc2, I have no idea why my EOL 
characters didn't make it? 
 
 
Text after many EOLs. 
 
Cheers. 
 

<offtopic>     
FYI: I did use EOLs in the previous large single line post. The only thing that was 
different was     
that I wasn't logged in when I typed the comment. When I clicked "Commit" I was asked     
to login and the message was passed. The EOLs I typed by hand were at locations:     
     
1.   1. People refusing...    
2.  2. I do not...   
3.  Further, if ...  
4.  Another thing... 
 
etc... 
     
Cheers.     
 

I will consider it.  

Subject: Re:  User Agent needs to contain "Konqueror/3.1"

On November 12, 2002 10:47 am, you wrote:
> ------- Additional Comments From mueller@kde.org  2002-11-12 16:47 -------
> I will consider it.

Thank you.

I can't stress enough how great it would be if I could email a website that 
was "dis'ing" Konqueror and tell them that all they have to do is have their 
JavaScript detect "Konqueror/3.1" and set their _ie6 var (or NS6_1 var) to 
true. 

So many sites use the User Agent to determine how to best render a page. 
Without a "Konqueror/3.1" string I do not know what to tell them to support 
Konqueror.

Cheers.

on the other side it will break sites that use Konqueror/3 now for enabling 
the support.  

Subject: Re:  User Agent needs to contain "Konqueror/3.1"

On November 14, 2002 05:39 pm, you wrote:
> on the other side it will break sites that use Konqueror/3 now for enabling
> the support.

I do not believe people are special-casing Konqueror and specifically enabling 
features.

I believe the uses of detecting Konqueror are:
1. degrade generated HTML output
2. block access to Konqueror

Also, in 99% of the sites I've come across all of the JavaScript tests for IE, 
Netscape 4.x, and Mozilla. Konqueror is just being lumped in with browsers 
that are not one of these three.

Detecting "Konqueror/3" will still work even if it becomes "Konqueror/3.1".

I believe people need a reason to support Konqueror, and that it has to be 
easy to support it if there is a reason. A good reason for most sites would 
be users requesting Konqueror support. To make it easy, if they can detect 
Konqueror/3.1 they can then set their _mozilla=true or _ie6=true and be done 
with it.

I worry that if it is not easy and they have to put up with 3.0 vs 3.1 
incompatibilities they will not support Konqueror.

Subject: kdelibs/kio/kio

CVS commit by mueller: 

UserAgent string Konqueror/3 -> 3.1. is backward compatible, so shouldn't
break anything. 
after long discussion..

CCMAIL:50388-done@bugs.kde.org


  M +2 -2      kprotocolmanager.cpp   1.122
  M +0 -3      kprotocolmanager.h   1.68