Note that this issue doesn't seem to occur when "renderAsPopup=true" and the same types of date or time selections are made in the popup calendar, with the exception that in Chrome if you select a date it still loses focus, but not if yo select a time.

In popup, submit occurs only when OK button is clicked. Nothing else is done by us when a date is selected. The date select event is all handled by YUI calendar.

Single submit doesn't seem to work anymore?

Single submit working again after svn update.

After setting single submit to false, selecting a date still loses focus, but in a different way. (Tabbing seems to set focus at a random link within calendar, instead of going outside calendar.) Selecting a time field doesn't lose focus anymore.

Same with ARIA disabled.

Same problem in the YUI calendar quick start tutorial, therefore it may be a problem in the YUI calendar itself.

http://developer.yahoo.com/yui/examples/calendar/quickstart.html

It's not a bug; it's a feature. Deep inside the date select event handler is this code:

if (link)

The result of blur() is also browser dependent? Need to override this behavior.

After overriding YUI calendar's link.blur() behavior AND commenting out ice.se(), keyboard focusing works as expected. See video at http://screencast.com/t/Fb2nwji7s.

However, if we put ice.se() back in, focus is lost again. So ice.se() is the second source of the problem that needs to be fixed.

Revision: 23742

Modified : /icefaces2/trunk/icefaces/ace/component/resources/org.icefaces.component.datetimeentry/calendar.js

Mircea, please review the latest code to see why the ice.se() call is losing focus in this case. If it's not an obvious fix we can discuss with Yip, etc.

After debugging the JS code I discovered that the call made to ice.component.calendar.updateProperties() function causes the focus to be lost. The function is called when the returned DOM update is applied, more precisely the script element containing the call to the function is evaluated.
While debugging further I could see how the entire HTML table representing the calendar widget is removed/destroyed and the re-added to the document. The removal of the table containing the element owning the focus is obviously the cause of the problem. Commenting out the code that destroys the table seems to fix the issue (although I don't know with what implications):

updateProperties: function(clientId, jsProps, jsfProps, events) {
Event.onContentReady(clientId, function(){
// console.log("jsProps =", JSON.stringify(jsProps, null, 4));
// console.log("jsfProps =", JSON.stringify(jsfProps, null, 4));
// logger.log("In updateProperties()");
// logger.log("renderAsPopup = " + jsfProps.renderAsPopup);
var context = ice.component.getJSContext(clientId);
// if (context && context.isAttached()) {
// var prevProps = lang.merge(context.getJSProps(), context.getJSFProps());
// var currProps = lang.merge(jsProps, jsfProps);
// for (var prop in currProps)

// }
ice.component.updateProperties(clientId, jsProps, jsfProps, events, this);
}, this, true);
}

The time selection works fine because in the DOM update received there's also an 'eval' command that applies focus back on the element submitting the time, namely the select element.

See comments in ICE-6466.

Revision: 23816

Modified : /icefaces2/trunk/icefaces/ace/component/resources/org.icefaces.component.datetimeentry/calendar.js
Modified : /icefaces2/trunk/icefaces/ace/component/src/org/icefaces/component/datetimeentry/DateTimeEntryRenderer.java