Bug 13845 - there is no way with WebKitQt to load urls from the Qt Resource System
Summary: there is no way with WebKitQt to load urls from the Qt Resource System
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 523.x (Safari 3)
Hardware: Other Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-23 09:39 PDT by sebastien le faou
Modified: 2007-10-17 05:36 PDT (History)
1 user (show)

See Also:


Attachments
a solution to this bug (3.34 KB, patch)
2007-05-23 09:43 PDT, sebastien le faou
mjs: review-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description sebastien le faou 2007-05-23 09:39:34 PDT
For example, If I want to load an image in a html page, there is no possibilities to reach one from memory, because we can only reach URLs.
So, it could be interesting to load data from the QT Resource System, ans add a URL protocol which allow to reach these data.
Comment 1 sebastien le faou 2007-05-23 09:43:32 PDT
Created attachment 14690 [details]
a solution to this bug

with this patch I can use URLs like that:

qrc:///my_path  or
:/my_path
Comment 2 Simon Hausmann 2007-05-29 00:25:50 PDT
IMHO just supporting qrc as scheme is fine, I don't think we should add hacks for supporting :/my_path. But does the qrc scheme support really need changes in KUrl? Shouldn't it be be possible to just detect that scheme in QWebNetworkInterface, strip it off and pass it through to the file loading?
Comment 3 Maciej Stachowiak 2007-05-29 01:00:24 PDT
I agree, this should be done in the Qt networking layer, not KURL. It's not appropriate for non-Qt ports to do special things for the qrc: scheme, and certainly doing :/some/path is not right/
Comment 4 Maciej Stachowiak 2007-05-29 01:00:34 PDT
Comment on attachment 14690 [details]
a solution to this bug

r=me
Comment 5 Maciej Stachowiak 2007-05-29 01:00:55 PDT
Er, I meant r-, not r=me

Comment 6 sebastien le faou 2007-05-29 15:18:55 PDT
ok, but I can't find QWebNetworkInterface class.
Are you sure it is the good class?
Perhaps there is now another name for this one???
Or that this is managed another way now?
Comment 7 George Staikos 2007-06-13 10:28:43 PDT
I think this should remain outside the porting layer.  It's quite easy to add new protocol handlers at the application layer.  This is quite specialized, and IMO no foreign content should be able to access application internals for content.
Comment 8 Mark Rowe (bdash) 2007-10-17 05:36:47 PDT
Closing as WONTFIX based on George's comments.