does HTTP extension work in plasma qml?

[Aaron J. Seigo]

On Tuesday, July 16, 2013 18:57:57 Sebastian Kügler wrote:
> On Tuesday, July 16, 2013 17:24:42 Marco Martin wrote:
> > On Tue, Jul 16, 2013 at 2:44 PM, Sebastian Kügler <sebas at kde.org> wrote:
> > > i have add line X-Plasma-RequiredExtensions=LaunchApp,HTTP in this qml
> > > plasmoid metadata.desktop is HTTP extension available in QML?
> > 
> > This is a little different in QML, you can load content from a http:// url
> > in many components without this extension. We are not able to sandbox QML
> > as we do with JavaScript, so our QML API, while being very similar to the
> > JS one, is less restrictive.
> > 
> > and, as we discussed today, we will be able again to filter and let/forbid
> > those things in qml2, since the url interceptor will intercept all url
> > requests, so we will  be able to say "no remote images"
> 
> Or even no remote images from facebook, but kde.org is fine. :-)

... just don’t mess with my pictures of cute kittens.

or better yet, replace all the pictures of sad things with kittens! ;)

really excited to see this in action, it’s one of the last missing puzzle 
pieces for being able to secure QML applications.

-- 
Aaron J. Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20130717/0909feee/attachment.sig>