There is an opportunity to improve the sophistication of the ace:submitMonitor in cases where multiple monitors are defined on the same page with overlapping scopes.

For example, an application may want to use a general monitor that activates for any submit on the page, blocks the entire page, and presents a general busy indicator while the submit is in progress. In addition, the application may also want to provide a more specific monitor on say, a particular form on the page ("ClaimForm"). In that case, if the "ClaimForm" submits, it's monitor would block only the form and present a custom message (e.g. "Submitting Claim...").

Currently, both monitors would be triggered by the submit of the "ClaimForm", which may be undesirable. A more sophisticated approach would have a submitMonitor with a more specific scope override any others with more general scopes. That way, multiple monitors could be setup on a page and only one of them would be activated by a given submit.