[webkit-qt] API proposal for handling (some) hybrid use cases
noam.rosenthal at nokia.com
noam.rosenthal at nokia.com
Tue Oct 11 14:20:16 PDT 2011
This is exactly along the lines of my thinking. Good work!
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.
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.
No'am
More information about the webkit-qt
mailing list