Repository navigation
fix(ui): resolve verified stale-state QA findings - #1909
JoeJoeflyn wants to merge 8 commits into
Conversation
Reuse existing theme watches, update listeners, bookmark persistence, and frame scheduling to repair seven verified findings without extra directory scans or status-only update requests. Preserve localized backend fallbacks and meaningful operation/device guidance. Refs #1862. Sidebar tint remains unconfirmed and unchecked.
Preserve the upstream menu-wheel and settle precondition instead of stacking two equivalent scroll actions. Keep the measured scenario cost and all preview, RTF, and document fixes from main.
|
Resolved and pushed the conflict with main in Post-merge validation: 9 selected Rust regressions and 10 QA runs passed; pinned formatting, Clippy, and whitespace checks passed. Earlier full-suite findings and their scoped recoveries are recorded in #1862; the full suites were not repeated merely to obtain a green summary. GitHub now reports mergeable=true. The PR remains draft: metadata checks pass, while full CI jobs are draft-gated/skipped, not passed. The requested before/after screenshots were shown in the conversation and copied into Seven original issue checkboxes are checked; sidebar tint remains unchecked/unconfirmed. No merge or ready-for-review action was taken. |
Reserve the accent fill for the current place and use one shared neutral hover rule for place and device rows. Keeping the pointer on the previous place after Alt+Up, Back, or address-bar navigation no longer resembles a second active location. Refs #1862
|
All eight findings are now implemented, with the last sidebar fix pushed as Whole-issue evidence and exact validation details: #1862 (comment). The complete local before/after gallery is The bounded final sidebar change passed four targeted QA runs plus pinned formatting/Clippy and whitespace checks. Earlier full-suite recovery and merge-validation results remain recorded; full CI is still draft-gated/skipped, not passed. The original issue checklist now marks all eight verified on this branch, not merged or released. |
Reuse the existing 寬鬆 wording from the density status for its Airy preset button. Keep the remaining eleven reviewed catalogs unchanged. Refs #1862
Request changesThis fixes the eight stale-state items from #1862: Omarchy palette rebind, shared update-check results, hidden files staying in the monitor, g+ pin slot feedback after bookmark publication, breadcrumb widths and scroll, density snap labels, a translated generic network error, and sidebar hover versus active. Two user-visible gaps should be fixed before merge. Check now clears other Updates rows
Keep the last rendered offer on rows that did not start this check, or publish an in-flight state. Clear only the sidebar notice immediately.
|
Starting a check cleared the shared result and reset every bound Updates row to idle, so a second Settings window lost its install offer until the new result arrived. Only the sidebar notice and the shared result are cleared now; rows that did not start the check keep their last rendering. Startup checks also published the raw channel preference while rows filter on the effective channel, so Pacman and Omarchy installations with a non-stable preference ignored the startup result.
GVfs SMB reports refused credentials as G_IO_ERROR_FAILED with the reason only in its message. Mount retries already recognised those phrases; location validation and directory listing now show the Permission denied catalog text for them instead of the generic system error.
The sidebar follows browser model events, so repeating the navigation routes per view mode exercised nothing new.
ReviewMerged Fixed (from the request-changes feedback)
Test and comment audit
Not changed (non-blocking notes)
VerificationNative headless tests ( |
Description
Resolve all eight findings from #1862 by reusing existing watch, listener, bookmark, and frame helpers:
Extend existing behavioral coverage and retain main's scroll-before-click precondition in the media-Properties scenario. Sidebar navigation state was already correct; its nearly identical hover/active styling caused the apparent double selection.
Visual evidence
How to test
colors.toml.g +; inspect confirmations for slots 1–4, 9, an unnumbered tenth pin, and a duplicate.Expected result: Changes stay live without refresh/restart or redundant update requests; pin confirmations reflect saved slots; breadcrumbs and presets remain usable; only the current sidebar location has the accent fill; network errors use localized application wording without exposing URI secrets or losing actionable guidance.
Related issue
Closes #1862.