This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
See the following example (in Chrome): http://jsbin.com/wiqutiku/1/quiet Imagine if <input type="date"> element was implemented as a custom element. The author would need to create the custom focus behavior this element has. Special behavior occurs when focus enters and leaves the element. When focus enters the element in the forward navigation direction, the element needs to focus the month field. When the focus enters the element in the backward direction, the element needs to focus the year field. When the focus leaves the month field in the backwards direction, the element needs to shift focus from itself to the previous element in the focus flow. When the focus leaves the year field in the forward direction, the element can simply let the focus naturally flow to the next element. Here's a strawman for one way this could work: - add willFocusCallback and willBlurCallback custom element callbacks and provide the focus navigation direction and currently focused element as arguments. - add a way to tell the platform to focus the 'next' or 'previous' element in the focus flow.
This is in progress in Blink implementation - design doc at https://docs.google.com/a/chromium.org/document/d/1k93Ez6yNSyWQDtGjdJJqTBPmljk9l2WS3JTe5OHHB50/edit
Moved to https://github.com/w3c/webcomponents/issues/150