Mike:
Any progress or ideas on this one. I am finding no good way to handle
this issue. FireFox doesn't seem to have the same problem. Regarding
your comment, "to mitigate the issue you can simply not use the wait
cursor. You can override this via the CSS options of BlockUI", this
also doesn't appear to work for me. How would this be done. For
example:
$('#tabs-nav').block({
message: '<div><img src="../App_Themes/
Images/loading_tab.gif" /> Updating please wait. . .</div>',
overlayCSS: {
backgroundColor: '#fff',
opacity: 0.2
},
css: { border: '2px solid #00447C' }
});
I have tried adding to both the overlayCSS and css overrides a cursor
of 'default' but it doesn't seem to do anything.
Thanks
On Sep 25, 7:14 am, Mike Alsup <mal...@gmail.com> wrote:
> > > Yes, same problem I posted yesterday... funny we both hit it this
> > > week. hopefully someone can help?? I know the author ofblockUI
> > > says he monitors this forum...
>
> Hmm, anyone have any ideas for how to force IE to honor the newcursor
> style without having to move the mouse? One that doesn't involve
> putting a mouse listener on the document.
>
> To mitigate the issue you can simply not use the waitcursor. You can
> override this via the CSS options ofblockUI.
>
> Mike
