Issue 2 (Chrome only)
A submitMonitor has it's blockUI attribute set to a panelGroup which holds a dataTable, this dataTable is where the submit comes from (via pagination). The submitMonitor also has it's for attribute set to the same panelGroup. In this scenario, no overlay is present and the submitMonitor renders slightly off center. This is Chrome browser only.
To reproduce:
1) 1) Build / deploy test application located at: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Manual/submitMonitor
2) In Chrome, navigate to '/submitMonitorFor.jsf'
3) Scroll down to the test at the bottom (ace:dataTable with ace:ajax 'page' event)
4) Change the blockUI to 'panelGroup5'
5) Trigger submitMonitor busy state using the dataTable pagination
6) Notice no overlay can be seen on the page and the submitMonitor is not centered.

was:
Issue 1 (All browsers)
When the blockUI attribute is set to the ID of a component, the overlay is misaligned when autoCenter is set to false. This is likely due to positioning the overlay first and the submitMonitor second, when the submitMonitor can affect the overlay positioning.
To reproduce:
1) 1) Build / deploy test application located at: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Manual/submitMonitor
2) Navigate to '/submitMonitorDynamic.jsf'
3) Select rendered, de-select autoCenter, and select box
4) Trigger submitMonitor busy state using the submit button
5) Notice that overlay is misaligned over the div

Issue 2 (Chrome only)
A submitMonitor has it's blockUI attribute set to a panelGroup which holds a dataTable, this dataTable is where the submit comes from (via pagination). The submitMonitor also has it's for attribute set to the same panelGroup. In this scenario, no overlay is present and the submitMonitor renders slightly off center. This is Chrome browser only.
To reproduce:
1) 1) Build / deploy test application located at: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Manual/submitMonitor
2) In Chrome, navigate to '/submitMonitorFor.jsf'
3) Scroll down to the test at the bottom (ace:dataTable with ace:ajax 'page' event)
4) Change the blockUI to 'panelGroup5'
5) Trigger submitMonitor busy state using the dataTable pagination
6) Notice no overlay can be seen on the page and the submitMonitor is not centered.

For issue 1, with autoCenter=false, and the alignment of the overlay over an element that appears below where the submitMonitor will show up, I fixed this by first positioning the submitMonitor, which can affect the page layout, and then position the overlay. Previously it had been the overlay first.
icefaces3 trunk
Subversion 31662
For issue 2, with Chrome, the overlay has width and height of zero, and the popup is mis-positioned, so likely there is a problem with getting the sizing of the panelGroup that they're being positioned over. Investigating further..

Issue #2 is spun off into its own jira ICE-8746.

Issue 1 is fixed in 3.2.

Assignee Priority: (was: P1)