This is a P3 - workaround is easy, use the mouse instead.

Can you clarify?  What I'm seeing is that as you use the up and down keys there is a perceived loss
of focus when you move from a named driver to "New Driver...", or from "New Driver..." to a named driver.
The remainder of the keyboard navigation here looks right to me.

Let me know if this is what you mean, or if not please clarify.  Thanks.

Nevermind.  I see what you're describing.  Hitting enter does not select "New Driver...".

Have you also seen the focus "gap" that I described?

I have the fix.

The focus gap I was describing appears to be that the separator (the separator between the named drivers
and "New Driver...") isn't rendering.  I'm running on a Mac.  Is this separator supposed to render?

I didn't try on Mac, but for me this issue reproducible not only by attempt to move from "New Driver..." to named or
vise versa, it is reproducible when I try with Up and Down keys choose any driver in drop down list.

Wow.  That IS bad.  The bug I found looks like it could introduce a timing error which may be
responsible for the behavior being different on various systems.  What platform have you seen
the worst of this?  I can try to validate my fix on another platform. 

I'm pretty sure I have the navigation fixed.  The bug is not in the connection dialog,
it's actually in DataComboBoxSupport.  

I'd like to address the separator between the named drivers and "New Driver...".  There are
multiple bugs there.  The first one is that it doesn't render, at least not on all platforms.
The second problem is that when using keyboard navigation it doesn't move the selection
to the next, or previous, item in the list as appropriate.  This results in the combo box appearing
to have lost focus when that is not the case.

I'm proposing to simply eliminate the separator.  It will simplify things here.  However, if we
want to retain it, I'd suggest opening a separate issue.  So on the Mac it doesn't currently render.
Does it render on Windows?  Linux?  Solaris?

Simplifying things by removing the separator makes sense to me, rather than spending all our time trying to fix this on
the various platforms.

Will do.  

BTW I'm not sure it renders on any platform.  I'd like to know the answer to that
anyway.

11547f9bf607

Integrated into 'main-golden', will be available in build *200810300201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/11547f9bf607
User: Rob Englander <mindstream@netbeans.org>
Log: #150216 Corrected the keyboard navigation for the drivers combobox in the New Connection dialog.  Also removed the separator, which did not work and caused the user to think the component had lost focus.

Verified with build 081030.

Since this issue is P3 priority, in accord with rules "How to include issues into patch"
(http://wiki.netbeans.org/NetBeansPatches) it must include an explanation as to why its backport is necessary and how
safe it is.

Could you please provide such explanation?

This issue is important to have since it is A11Y related issue and if customer use only keyboard, it can be very, very
annoying to add new connection.
And this issue was P2 in the beginning and therefore I added status whiteboard.
But if anybody think that it is rare case, then I can remove status whiteboard.
Rob, could you tell how the fix is safe?

The fix is highly isolated.  It is only in the code that handles the events that are raised by that combobox.  It is
very safe as the code now follows standard event handling instead of having multiple handlers as it had before.

I've transplanted the changeset http://hg.netbeans.org/main/rev/11547f9bf607 into release65_fixes repository as
http://hg.netbeans.org/release65_fixes/rev/ed7fb0ebcd05