[thejambi]

In the New UI detail view, a section that offers commands (a sense, Variants, Allomorphs, a Notebook record's Subrecords and others) now shows one small button per command at the right of its header line, such as "Insert Example" and "Insert Sense" on the sense being edited. The buttons appear on the section holding the current field, as WinForms shows its blue links only on the active section. A section that is empty or collapsed shows them all the time, since it has no field to click or Tab into. Each button is a Tab stop, reached with Shift+Tab from the section's first field.

Until now each such header carried a single "Field Options" link that opened a menu of the commands, so the commands could not be seen at a glance and every insert took two clicks.

Headless control-level capture, not FLEx. Only the section holding the caret shows its buttons.

Reviewer notes

Why one section at a time. WinForms sets SummarySlice.Active from Slice.SetCurrentState, so its links show only on the current section. Showing buttons on every section was considered and rejected as visual noise on long entries. The rule is recorded as UX-9 in Docs/ux/README.md (provisional, superseding UX-2 and UX-3); user testing asking for buttons everywhere is the trigger to revisit it.

Deliberate rules.

• The section a field belongs to is its nearest enclosing header with hotlinks (DetailVisibility.GetHotlinksHeaderIndex), passing over headers without any. The Avalonia Header kind also covers group headers and sequence banners, where passing over matches WinForms. WinForms stops at the first header="true" slice, so a nested header="true" section with no hotlinks of its own would differ; no shipped layout is known to have one.
• The buttons are Tab stops, unlike WinForms' painted links. The section header and its "..." button are not Tab stops (LT-22688), and the main Insert menu lacks some of these commands (Insert Example, Insert Reversal Subentry), so the buttons are the keyboard's only way to them inside the view. The "Field Options" link they replace was a Tab stop for the same reason.
• An empty or collapsed section shows its buttons at all times (DataTree.UpdateHotlinks, re-run after every visibility change and every change of section), since focus cannot enter it to bring them. An independent review after preflight found that an empty Variants or Subentries section had lost its keyboard route; fixed in 2d76c31.
• Commands are fetched when a section's buttons are shown, not on every focus change within it, so a button is never rebuilt under the pointer. Enabled state is not refreshed while focus stays in the section; WinForms re-checks on a timer. Accepted as a known difference.
• Lexicon hotlink menus are answered by the native command authorities, with live enabled state. Menus no authority owns yet (Notebook's) are listed from configuration, shown as enabled, and resolved on click through the hidden command adapter by label, with the same "not available" message WinForms shows. That listing includes submenu commands and is not filtered by display handlers; no shipped hotlinks menu is affected.
• Buttons that do not fit are dropped from the right and leave the Tab order, rather than wrapping or clipping half a label. They stay in the UI Automation tree at zero size, so a screen reader could list them; hiding them needs a custom automation peer and is deferred.
• The tint overrides Semi's ButtonDefault*Background keys on each enabled button. Semi draws a disabled button with its resting fill, so an unavailable command keeps the neutral grey. A Semi rename of those keys would drop the tint silently; Hotlinks_AreTinted_... would catch it.
• Leaving an edited field autosaves and re-shows the view. Focus memory brings back the remembered button's section, then its focus and focus ring (0a53649, 4d6fcf1).
• The two new strings, ksHotlinkCommandUnavailable and ksHotlinkCommandDisabled, copy the wording of DetailControlsStrings.ksCmdUnavailable and ksCmdDisabled, which are internal to DetailControls. They show in English until Crowdin translates them.
• API: DataTree and DetailHostControl.ShowDetail gain an optional trailing hotlinkItems parameter. New theme tokens DataTree.HotlinkGap, HotlinkPadding and HotlinkCornerRadius. Automation ids: <row>.Hotlinks names the strip and <row>.Hotlinks.<n> each button; nothing in the repo automated the old single link.

The look. Five candidates were captured headlessly, all in the same place; the tinted buttons (3) were chosen. WinForms draws underlined links (1). Plain links (2) read as text, outlined chips (4) were less obviously primary, and a plus with a label (5) implies "add", which does not fit commands such as Show Concordance. Keeping the "Field Options" link beside the buttons was rejected, since its menu would repeat them on the same line.

Headless control-level captures of a throwaway restyling; only look 3 exists in the code.

Headless control-level capture. Pointer over the first button; the second command cannot run.

Tests. DetailHotlinkTests covers the section rule, buttons following focus between sections and staying put within one, one button per command with its enabled state, click, Shift+Tab then Enter, Tab into a section landing on its first field, empty and collapsed sections showing their buttons (Tab reaches them, and focusing one does not rebuild it), overflow leaving view and Tab order, tint, hover and unavailable states, and position on the header line. DetailFocusMemoryTests.ReshowWithNoRequest_KeepsFocusOnTheRememberedHotlink fails without 0a53649 and checks the focus ring. LexiconMenuExecutionTests runs Insert Sense from the button's own item and checks where the sense lands, plus the unowned-menu listing. Not covered: the Notebook click path through the hidden adapter (manual test 1). FwAvaloniaTests: 974 passed, 1 pre-existing skip. xWorksTests menu and command fixtures: 171 passed. Comment and token hygiene are clean.

Manual tests. Done, with New UI mode on:

1. Notebook: the Subrecords section's "Insert Subrecord" button adds a subrecord.
2. Lexicon Edit: type in a Gloss and press Shift+Tab; after the view refreshes, "Insert Sense" (the last button) has keyboard focus and its focus ring, and Enter adds a sense.

Not done: on an entry with no variants, Tab from the field before Variants onto "Insert Variant" (covered headlessly by AnEmptySection_ShowsItsHotlinks_WithoutFocus_AndTabReachesThem).

Out of scope. commandVisible="true" (the Words tool's wordform header, not yet on this view); refreshing enabled state while focus stays in a section; insert speed, since each insert recomposes the entry and rebuilds the view (a follow-up).

🤖 Generated with Claude Code

---

This change is

[github-actions]

NUnit Tests

    1 files  ± 0      1 suites  ±0   14m 13s ⏱️ -4s
7 078 tests +27  6 993 ✅ +27  85 💤 ±0  0 ❌ ±0 
7 087 runs  +27  7 002 ✅ +27  85 💤 ±0  0 ❌ ±0 

Results for commit 2d76c31. ± Comparison against base commit 9c931ec.

This pull request removes 4 and adds 31 tests. Note that renamed tests count towards both.

FwAvaloniaTests.DetailMenuRequestTests ‑ HotlinksStrip_Activating_RaisesTheSameHotlinksRequest_AsTheKebab
FwAvaloniaTests.DetailMenuRequestTests ‑ HotlinksStrip_AppearsForHotlinkHeader_IsAlwaysVisible_AndKeepsTheKebab
FwAvaloniaTests.DetailMenuRequestTests ‑ HotlinksStrip_IsAbsent_ForHeaderWithoutHotlinks
FwAvaloniaTests.DetailViewingParityTests ‑ SectionHeaderAndFieldOptionsText_TakeTheirOwnSizeAndColour

FwAvaloniaTests.DetailFocusMemoryTests ‑ ReshowWithNoRequest_KeepsFocusOnTheRememberedHotlink
FwAvaloniaTests.DetailHotlinkStripTests ‑ ACollapsedSection_ShowsItsHotlinks_UntilItIsExpanded
FwAvaloniaTests.DetailHotlinkStripTests ‑ AHeaderWhoseMenuOffersNoCommand_ShowsNoLinks
FwAvaloniaTests.DetailHotlinkStripTests ‑ AnEmptySection_ShowsItsHotlinks_WithoutFocus_AndTabReachesThem
FwAvaloniaTests.DetailHotlinkStripTests ‑ ClickingAHotlink_RunsItsCommand
FwAvaloniaTests.DetailHotlinkStripTests ‑ Hotlinks_AreReachedWithShiftTab_FromTheSectionsFirstField_AndRunWithEnter
FwAvaloniaTests.DetailHotlinkStripTests ‑ Hotlinks_AreShown_OnlyWhileFocusIsInTheirSection
FwAvaloniaTests.DetailHotlinkStripTests ‑ Hotlinks_AreTinted_AndDeepenTheTintUnderThePointer_ButNotWhenDisabled
FwAvaloniaTests.DetailHotlinkStripTests ‑ Hotlinks_FollowFocus_FromOneSectionToTheNext
FwAvaloniaTests.DetailHotlinkStripTests ‑ Hotlinks_RenderCleanly_OnTheActiveSensesLine
…

♻️ This comment has been updated with latest results.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 83.73984% with 40 lines in your changes missing coverage. Please review.
✅ Project coverage is 40.54%. Comparing base (8afbeb5) to head (2d76c31).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
...xWorks/Avalonia/Hosting/RecordEditView.Avalonia.cs	37.83%	21 Missing and 2 partials ⚠️
Src/Common/FwAvalonia/Detail/DetailHotlinkStrip.cs	93.69%	2 Missing and 5 partials ⚠️
Src/Common/FwAvalonia/Detail/DataTree.cs	91.22%	1 Missing and 4 partials ⚠️
Src/Common/FwAvalonia/Detail/DetailVisibility.cs	83.33%	1 Missing and 2 partials ⚠️
Src/Common/FwAvalonia/Detail/DetailFocusMemory.cs	90.90%	0 Missing and 1 partial ⚠️
Src/Common/FwAvalonia/DetailHostControl.cs	50.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1232      +/-   ##
==========================================
+ Coverage   40.50%   40.54%   +0.03%     
==========================================
  Files        1559     1560       +1     
  Lines      356085   356279     +194     
  Branches    41584    41626      +42     
==========================================
+ Hits       144243   144446     +203     
+ Misses     182531   182510      -21     
- Partials    29311    29323      +12     

Files with missing lines	Coverage Δ
Src/Common/FwAvalonia/FwAvaloniaDensity.cs	97.29% <100.00%> (+0.28%)	⬆️
...AvaloniaTheme/Tokens/DataTree/DataTreeTokens.axaml	100.00% <100.00%> (ø)
Src/Common/FwAvalonia/Detail/DetailFocusMemory.cs	74.05% <90.90%> (+0.78%)	⬆️
Src/Common/FwAvalonia/DetailHostControl.cs	70.27% <50.00%> (+0.82%)	⬆️
Src/Common/FwAvalonia/Detail/DetailVisibility.cs	88.88% <83.33%> (-1.24%)	⬇️
Src/Common/FwAvalonia/Detail/DataTree.cs	92.48% <91.22%> (-0.63%)	⬇️
Src/Common/FwAvalonia/Detail/DetailHotlinkStrip.cs	93.69% <93.69%> (ø)
...xWorks/Avalonia/Hosting/RecordEditView.Avalonia.cs	62.05% <37.83%> (-1.26%)	⬇️

... and 15 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.