incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Mueller <>
Subject Re: new iOS command queue may have broken innerHTML fix
Date Tue, 25 Oct 2011 21:39:43 GMT
Perhaps we need to go the android route, implement a minimal in-process HTTP
server, and XHR our messages from JS to ObjC.

On Tue, Oct 25, 2011 at 16:51, Becky Gibson <> wrote:

> However, I think our new queuing mechanism may have broken that.  We do
> create an iframe and set gap://"ready" to trigger reading the commands from
> the queue. However, we always use the same iframe and don't delete and
> recreate it.

Have we tried with a lighter-weight element, like <img>?  (setting the src
attribute).  I'm always leering of using iframe's on mobile anyway, because
I believe you are limited to a small number of iframes on your page in the
first place - not that users should be using iframes for anything, but

I'm not sure if that is the problem or if it is because we are now "pulling"
> the commands from objective-C rather than "pushing" them in through the
> iframe.src.

Do you mean the new "fast" messaging?  Seems like the problem is with the
signalling from the JS side to the ObjC side, not the data transfer.

Patrick Mueller

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message