In complex applications using $.blockUI extensively, different components may collide in their usage e.g. a $.blockUI call is set on a timer for long-running xhr, and an other one is set on a specific set of requests (rather than a single one) which is known to be a long "process" (e.g. with a progress bar and a bunch of calls to query the installation state).
if the first case is nested within the second one, or happens at the same time, it may end up cancelling the previous $.blockUI. It would be nice if a block could be set with an arbitrary key/password/passphrase, and only calling $.unblockUI with the same string unblocked the UI.
In complex applications using
$.blockUIextensively, different components may collide in their usage e.g. a$.blockUIcall is set on a timer for long-running xhr, and an other one is set on a specific set of requests (rather than a single one) which is known to be a long "process" (e.g. with a progress bar and a bunch of calls to query the installation state).if the first case is nested within the second one, or happens at the same time, it may end up cancelling the previous
$.blockUI. It would be nice if a block could be set with an arbitrary key/password/passphrase, and only calling$.unblockUIwith the same string unblocked the UI.