{"version":"2.1.281","anchor":"focus-non-focusable-tabindex-1-elements-redirect-focus-t","canonical_anchor":"focus-non-focusable-tabindex-1-elements-redirect-focus-t","heading":"Focus: non-focusable (tabIndex -1) elements redirect focus to a focusable ancestor","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/focus-non-focusable-tabindex-1-elements-redirect-focus-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Focus: non-focusable (tabIndex -1) elements redirect focus to a focusable ancestor\n\nFocusing a part of the screen that cannot take focus now moves focus to a nearby part that can\n\n**Unclear.** The finding does not say which screens or controls this affects in practice.\n\n**What**\n\nIn Claude Code's on-screen interface, some parts are marked as unable to take keyboard focus (with `tabIndex` set to -1). Trying to focus one of these now sends focus to a part that contains it and can take focus. That is the currently focused part, a recently focused one, or one set to take focus automatically.\n\n**Why**\n\nKeyboard focus lands on something that can use it instead of on a part that cannot."}