[webkit-qt] API proposal for handling (some) hybrid use cases
Caio Marcelo de Oliveira Filho
caio.oliveira at openbossa.org
Tue Oct 11 15:40:31 PDT 2011
On Tue, Oct 11, 2011 at 6:20 PM, <noam.rosenthal at nokia.com> wrote:
> This is exactly along the lines of my thinking. Good work!
Cool :-)
> I do have some comments.
>> window.postMessageToQt(input.value);
>
> Maybe instead, we should allow
> navigator.postMessage, and add it as a proposal to HTML5 window messaging? It just feels more natural.
Sounds like something we could try. "window" was used just because was
the simplest thing to make it work. OTOH, I was thinking about
exposing this in a Qt specific object, making the communication API
identical for WebScripts{} and the JS of the webpage.
> Also, we should be clear about what the origin fields should have in the message. There might be a security issue, since iframes might post messages to the parent window pretending to be the navigator.
> I'm thinking that messages to/from the UI container should always have a navigator:// URL to their origin, and in WebKit we can make sure those are not faked.
Ack! :-)
Thanks for the comments,
--
Caio Marcelo de Oliveira Filho
OpenBossa - INdT
More information about the webkit-qt
mailing list