[2.2.1] Using the calendar kills tabindex

I just noticed a bug (?) that occurs when I select a date using the datePicker. The date field is in focus (with the selected date as a value) but when I tab it doesn't go to the next form field, it goes to a navigation link at the top of the page - the first link in the html code!

Note that no fields or links on the page have a tabindex, so the standard/default tab order should be followed. This occurs only in Firefox (2 and 3).

Looks it's not just me then. I hope the EXT-support gurus can take a look at this and come with a code-fix or hack I can use to fix the problem. It kind of ruins the accessibility (use without mouse) of my form so I think it's important to resolve.

can't reproduce this in my app. the datepicker works as expected on FF3 / Safari.

[edit]could you post a simple a test case?
came up with a simple test case though -- the problem only manifests consistently when the form is long (i.e. when scrolling is involved) AND no explicit tabIndex exists for the form fields.

repeat the following steps with the spacer ux height set to 12 first, then 1200 (by fiddling with the comments in the quick-switch block in red):

click the datepicker icon

select a date

try tabbing to the next field -- focus goes somewhere, but not to the text field

additionally, once a date is picked using the datepicker, while the datefield is still focused, typing a date into the datefield's <input> field and then tabbing also moves the focus to somewhere on the page, but not to the text field.

the reason i'm not seeing this in my app (which has long scrolling forms) is because i programatically add a tabIndex to all my form fields.

It just needs to focus the input field on select of a date from the picker.

It doesn't work. The focus is set on the input field so I can change its value. When I try to tab to the next field - focus goes to the first element on the current browser (firefox 3) window, but not to the next component of the form.