You need to
before you can comment on or make changes to this bug.
I'm not sure this matters that much, since the old text field code will soon go away. Anyway, this is probably a simple fix.
Created an attachment (id=5967) [details]
test case added. Can't tab from the old field to the new field, but you can tab from the new to the old.
<rdar://problem/4463760> Can't tab from old text field to new text field (6811)
Bumping to P1 since this causes a text field regression
*** Bug 8122 has been marked as a duplicate of this bug. ***
These are all text field regressions so they should all be P1.
Created an attachment (id=7479) [details]
the fix is not so bad after all
(From update of attachment 7479 [details])
I'm sad that nextKeyViewInFrame still needs to have a side effect.
That having been said, this looks like a pretty good fix.
Looks like Hyatt already reviewed this and Maciej already landed it last night.