Skip to content

App 487: set the focus with cs_event-set_focus instead of the obsolete z2ui5.cc.Focus - #84

Merged
oblomov-dev merged 1 commit into
mainfrom
claude/peaceful-pascal-4z2w4v
Sep 27, 2026
Merged

oblomov-dev merged 1 commit into
mainfrom
claude/peaceful-pascal-4z2w4v

Conversation

@oblomov-dev

Copy link
Copy Markdown
Member

z2ui5.cc.Focus is marked OBSOLETE in the core; its replacement is the frontend action cs_event-set_focus.

  • z2ui5_cl_smps_app_487: the Focus control is replaced by client->follow_up_action( val = client->cs_event-set_focus t_arg = VALUE #( ( \inputApp` ) ) ), queued right after view_display( ). The now-unused xmlns:z2ui5` is removed.
  • Behaviour is unchanged: the control only ever focused once per view display.
  • 487's render-error exclusion in abap2ui5lint.jsonc is gone, so the app is render-checked now. catalogue-derived.json and the badge are regenerated.
  • npm run check is green: abaplint 0, linter plus render 0 findings.

🤖 Generated with Claude Code

https://claude.ai/code/session_014bLQZPXbB8xmewCNmnBJaG


Generated by Claude Code

The magic-key input got its initial focus from the invisible
z2ui5.cc.Focus control, which the core marks OBSOLETE. The view now
queues cs_event-set_focus as a follow-up action right after
view_display( ), which focuses the same input once the view has
rendered - the same one-shot-per-display behaviour the control had,
since its setUpdate was never bound.

The unused xmlns:z2ui5 declaration goes with it, and so does the
render-error exclude for this class: it no longer loads a framework
custom control, and the render gate now covers it. catalogue-derived.json
and the badge are regenerated (one control fewer).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014bLQZPXbB8xmewCNmnBJaG
@oblomov-dev
oblomov-dev merged commit d8ce62d into main Sep 27, 2026
23 checks passed
@oblomov-dev
oblomov-dev deleted the claude/peaceful-pascal-4z2w4v branch September 27, 2026 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants