Bug 13845 – there is no way with WebKitQt to load urls from the Qt Resource System

• Status: RESOLVED
• Resolution: WONTFIX
• Component: New Bugs

[sebastien le faou]

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.

[sebastien le faou]

Created attachment 14690 [details]
a solution to this bug

with this patch I can use URLs like that:

qrc:///my_path  or
:/my_path

[Simon Hausmann]

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?

[Maciej Stachowiak]

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/

[Maciej Stachowiak]

Comment on attachment 14690 [details]
a solution to this bug

r=me

[Maciej Stachowiak]

Er, I meant r-, not r=me

[sebastien le faou]

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?

[George Staikos]

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.

[Mark Rowe (bdash)]

Closing as WONTFIX based on George's comments.