I'm surprised by default keyboard navigation order...

# compose

[Andy Himberger]

I'm surprised by default keyboard navigation order, wondering if this makes sense to someone. If you have multiple focusable things in a row, I would expect default navigation order to go between the items in a row (navigate the common children of a parent) before going to the next one. Talkback navigation order does this, but keyboard tab does not.

[Andy Himberger]

If I do something like this, tab key will go vertical so its 1,1,1,2,2,2,3,3,3,4,4,4,5,5,5. I would expect tabbing to go 1,2,3,4,5,1,2,3,4,5 matching what talkback swipe forward does?

(Tested with compose 1.2.1)

[Zach Klippenstein (he/him) [MOD]]

I thought it used composition order for 1D traversal, but there's a lot of work going on here now so I'm not sure if this is expected. Can you repro on 1.3? If so, please file a bug.

[Andy Himberger]

Actually it does behave as expected with 1.3-alpha03, will just need to wait a bit until we can upgrade to it (Compile SDK 33 needs to be final released & compose 1.3 hit beta before we will adopt it in our app)

[Ian Lake]

FWIW, SDK 33 is final and has been for months: https://android-developers.googleblog.com/2022/06/android-13-beta-3-platform-stability.html

all app-facing behaviors and APIs, including the official API Level 33 SDK and NDK APIs, are now final

[Andy Himberger]

I guess I just had to post that, now today AOSP is released and source downloads are available