Change Type

Please check √ next to the corresponding type, only one option can be selected:

• feat (new feature, corresponds to Changelog Added)
• fix (bug fix, corresponds to Changelog Fixed)
• docs (documentation change, corresponds to Changelog Documentation)
• refactor (code refactoring, corresponds to Changelog Changed)
• perf (performance optimization, corresponds to Changelog Performance)
• test (test related, not included in Changelog)
• chore (build/toolchain/dependency, not included in Changelog)
• deprecated (mark deprecation, corresponds to Changelog Deprecated)
• removed (remove feature, corresponds to Changelog Removed)
• security (security fix, corresponds to Changelog Security)

Change Description

With ALL_CONTAINERS_CLICKABLE OFF, ArkUI lets a container take keyboard focus by itself only when NODE_ON_CLICK is registered before NODE_FOCUSABLE is written. View::onPropsChanged used to write NODE_FOCUSABLE for accessible before registering the click for focusable, so a View with both accessible={true} and focusable={true} could not take keyboard focus.

CustomNode::setClickRegistered registers or unregisters NODE_ON_CLICK and does not write NODE_FOCUSABLE. In OFF mode, the click registration follows the focusable prop only. NODE_FOCUSABLE is then set to accessible || focusable.

• accessible={true} alone writes NODE_FOCUSABLE and does not register a click. The View cannot take keyboard focus, and a screen-reader double tap stays a touch.
• accessible={true} with focusable={true} registers the click first, then writes NODE_FOCUSABLE. The View can take keyboard focus, and a screen-reader double tap is a click.
• focusable={true} registers the click and writes NODE_FOCUSABLE. The View can take keyboard focus, and a screen-reader double tap is a click.
• A View that needs keyboard focus while keeping the screen-reader double tap as a touch should leave focusable unset and mount its own focusable child.

ON mode is unchanged: the constructor still registers NODE_ON_CLICK, and setFocusable only writes NODE_FOCUSABLE.

This adds the internal C++ method CustomNode::setClickRegistered. No JS prop is added or removed. The behavior applies to RN View keyboard focus and screen-reader double tap when ALL_CONTAINERS_CLICKABLE is OFF. The same rules are documented in the Chinese and English usage FAQs.

Test Steps

Test reference: gtest: rnoh_customnode_focusable_test, rnoh_customnode_focusable_on_test, rnoh_view_ci_props_test, rnoh_view_ci_props_on_test

Host gtest files for this behavior are not on this version line. The same cases cover it on 0.84 and 0.86.

1. With ALL_CONTAINERS_CLICKABLE OFF, reach a focusable={true} View from the keyboard.
2. Confirm accessible={true} without focusable does not register NODE_ON_CLICK.
3. Confirm accessible={true} and focusable={true} registers click, then sets focusable.
4. Confirm ON mode behavior is not affected.

Test Status

• Passed local comprehensive testing (unit tests/integration tests)
• Passed CI automatic build and testing
• Added/updated corresponding test cases
• Verified functionality in target environment (e.g. phone/tablet)
• Verified availability on the minimum compatible API version

Pre-merge Self-Check

• Does not involve incompatible changes; if involved, has been reviewed accordingly.
• Does not impact performance, or performance testing has been conducted without degradation.
• Complies with the corresponding coding standards.
• No sensitive information leakage, such as passwords, keys, etc.
• Does not involve documentation updates, or documentation has been updated.
• Meets testability requirements with necessary self-test cases, appropriate logging, or trace information added.
• No illegal file inclusions, including images and code.

Linked Issue

Close #3539