makes complete sense now - thanks!
malsup wrote:
>
>
> rolfsf,
>
> The purpose of the caching is because when you invoke unblock() or
> unblockUI the blocking elements are removed from the DOM. That means
> you can't find them again with a jQuery selector, so they need to be
> cached or th
rolfsf,
The purpose of the caching is because when you invoke unblock() or
unblockUI the blocking elements are removed from the DOM. That means
you can't find them again with a jQuery selector, so they need to be
cached or they won't be reusable.
The difference between using an existing DOM el
Cool - thanks Mike. I guess I don't understand the purpose of the cacheing in
this case (my javascript knowledge is limited). When I've got my
proof-of-concept working correctly and pass it on to the engineers to
implement, I'll know better whether the div or the simple static message
works bette
rolfsf,
You need to take the same approach with the 2nd message as you did
with the first - cache it:
var question = $('#question')[0];
var wait = $('#wait')[0];
Then in your "yes" handler do this:
$('#myDiv').unblock().block(wait, {width: '275px'});
But if you're just displaying a simple st
4 matches
Mail list logo
