Communication between two frames now is synchronous, and in my opinion,
necessarily so. I believe (and I could be wrong) the intent of postMessage()
was to allow similar access between frames of different origins as there is
between frames of the same origin. If that's the case, then making
On Sun, Apr 6, 2008 at 1:52 AM, Aaron Boodman [EMAIL PROTECTED] wrote:
There doesn't seem to be any advantage to it.
I take it back, there is one advantage, which Jeff brought up:
function realMessageHandler(messageEvent) {
// handle the message...
// and, reply to the message
Having worked with the canvas tag quite a bit now, I've found that it
is a bit awkward that the canvas tag is not taking advantage of CSS.
If you are changing your site design, perhaps you want to change the
colors used in your line graphs as well. So you make the changes in
your CSS for the
Here is one more point on the async vs sync thing.
In my opinion, one of the most compelling reasons to make an API
synchronous instead of asynchronous is convenience. This is why I was
so passionate about having a synchronous database API: getting the
result of a call via a return value is much
On Sun, Apr 6, 2008 at 1:52 AM, Aaron Boodman [EMAIL PROTECTED] wrote:
We have on one hand authors with reasons
(however edge casey you may believe them to be) they would prefer the
API be asynchronous,
Here's another problem an async API would automatically address:
On Sun, 06 Apr 2008 11:41:20 +0200, Peter Kasting [EMAIL PROTECTED]
wrote:
Here's another problem an async API would automatically address:
https://bugzilla.mozilla.org/show_bug.cgi?id=416912
FWIW, Opera is ok either way. I personally think it doesn't make much
sense for this to be
On Sun, 06 Apr 2008 10:49:01 +0200, Greg Houston
[EMAIL PROTECTED] wrote:
Having worked with the canvas tag quite a bit now, I've found that it
is a bit awkward that the canvas tag is not taking advantage of CSS.
If you are changing your site design, perhaps you want to change the
colors used
Peter Kasting wrote:
Here's another problem an async API would automatically address:
https://bugzilla.mozilla.org/show_bug.cgi?id=416912
That *should* be handled by a slow-script dialog, and the fact that it isn't is
simply a bug. That the bug is triggered using postMessage is in my opinion
