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?
(If it's just a single image tag that's rendering, you could always do a
onload attribute on that element...)
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.
Jim
On 5/24/09 5:03 PM, David Geary wrote:
I have an Ajax request that pulls an image from a web service.
I'm using
f:ajax's onevent attribute to display a progress bar when the Ajax call
begins, and make it disappear when the call is complete, but complete
does not coincide with the end of rendering, so there's sometimes a
considerable lag between when the progress bar disappears, and when the
image is fully drawn.
Is there a way to send a notification when rendering is complete, so I
can avoid the lag time?
Thanks,
david