<div>Anne-<br></div><div><br></div><div>Thanks for the reply.</div><div><br></div>I see window.postMessage as different from element.dispatchEvent. The JS author has control over the JS code executed as a result of their dispatchEvent call. JS author does not have control over code executed by window.postMessage (either before and after, or during the call).<div>
<br></div><div>- I know what the JS stack looks like before my dispatchEvent call, but with postMessage the JS stack exhaustion threat exists (as mentioned in my previous email).</div><div><br></div><div>- With dispatchEvent, I control what the event handler code does. With window.postMessage I may wait for an indeterminate amount of time for that other frame's code to complete.</div>
<div><br></div><div>These issues (and the ones mentioned in my previous email) go away if postMessage is made async.</div><div><br></div><div>-eric</div><div><br><div><br><div class="gmail_quote">On Fri, Apr 4, 2008 at 2:39 PM, Anne van Kesteren <<a href="mailto:annevk@opera.com">annevk@opera.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">On Fri, 04 Apr 2008 23:04:30 +0200, Eric Seidel <<a href="mailto:eric@webkit.org" target="_blank">eric@webkit.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8x;border-left:1px #ccc solid;padding-left:1ex">
Anyway, I'm not the foremost expert here, but I was reading HTML5 last week and encountered this sync postMessage() requirement, which seemed like a bad idea.<br>
</blockquote>
<br></div>
It doesn't make sense to change this given that all synthesized event dispatching is synchronous. I don't think postMessage() should be different.<br><font color="#888888">
<br>
<br>
-- <br>
Anne van Kesteren<br>
<<a href="http://annevankesteren.nl/" target="_blank">http://annevankesteren.nl/</a>><br>
<<a href="http://www.opera.com/" target="_blank">http://www.opera.com/</a>><br>
</font></blockquote></div><br></div></div>