<br><br><div class="gmail_quote">On Sun, May 24, 2009 at 8:40 PM, Jim Driscoll <span dir="ltr"><<a href="mailto:Jim.Driscoll@sun.com">Jim.Driscoll@sun.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You know, that's a really good question - I don't think we considered that use case. Probably because we were expecting the rendering process itself to not take a really noticeable amount of time. Other than rendering a new image component, or a complex canvas, or a really complex table, I can't imagine it taking all that long - what are you rendering?<br>
<br>
(If it's just a single image tag that's rendering, you could always do a onload attribute on that element...)<br>
<br>
Though I haven't tested it, I think that a rendered event isn't going to help you anyway if it's an image, since the image itself will be loaded out of band (I think) after the DOM is updated, and the rendered event will have long before fired off... more or less mimicking what you're already seeing.</blockquote>
<div><br>I believe you are describing the situation perfectly. The rendering of the image is really not part of the Ajax request at all. The main issue is that the onload even of an image was never standardized in HTML (to my knowledge), which is such a pain point of HTML. However, I do know that it works in most browsers.<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>