Bug 91682 - KStringHandler / KHTMLPart / KApp::invokeBrowser inconsistency
Summary: KStringHandler / KHTMLPart / KApp::invokeBrowser inconsistency
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2004-10-19 15:31 UTC by Rob Kaper
Modified: 2018-10-21 05:01 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Kaper 2004-10-19 15:31:32 UTC
Version:           unknown (using KDE 3.3.0, compiled sources)
Compiler:          gcc version 3.3.3 [FreeBSD] 20031106
OS:                FreeBSD (i386) release 5.2.1-RELEASE

There are some inconsistencies between the various URL handling parts in kdelibs:

1: take arbitrary text and run it through KStringHandler::tagURLs(body);

2: take the output html and put it into a khtmlpart

3: connect to the khtmlpart's browserextension's openURLRequest signal

4: plug that url into kapp->invokeBrowser

Step 2 creates an anchor for phrases such as www.blah.com, but such URLs don't work in step 4, presumably because of the lacking protocol.
Comment 1 lexual 2010-01-23 07:28:54 UTC
Is this still relevant to recent KDE version?
If not please close the bug.

Thanks,

Lex.
Comment 2 Andrew Crouthamel 2018-09-20 21:58:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-21 05:01:48 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!