In Chrome, the bridge code seems not to be calling setFocus() when <input type="submit"/> and <button> elements are clicked/focused. Thus, the last element for which setFocus() was called before pressing the button (and sending a request) will have focus reapplied to it when the response comes to the client. In the particular case of ace:dateTimeEntry in the popup-mode, this will cause the calendar to pop up every time the submit button is pressed.

For example, in Chrome, in the ace:dateTimeEntry max/min demo, when you click on the maximum date calendar, you'll see this message in the console, as expected:

[window] persisted focus for element "form:maxIn_input"

This means that setFocus() was invoked. However, when you click on the 'Submit Max/Min Dates' button, you WON'T see this message in Chrome:

[window] persisted focus for element "form:submitMinMax"

This means that setFocus() wasn't invoked for the command button in Chrome. Thus, the calendar will pop up when the response comes back. However, you will be able to see this message in FF and IE, and the calendar won't pop up every time the submit button is pressed.