fix(appearance): unify zoom controls with a configurable default - #1720
fix(appearance): unify zoom controls with a configurable default#1720rodboev wants to merge 21 commits into
Conversation
roborev: Combined Review (
|
bb9e9c4 to
a700645
Compare
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
Keep supported zoom percentages in one declaration so config validation, API schemas, and frontend controls cannot drift as choices change. Use the existing enum generator and preserve numeric JSON and TOML values.
roborev: Combined Review (
|
Settings requests could outlive appearance assertions and fail during browser teardown. Fetch the isolated settings fixture before navigation so route callbacks only serve the captured response.
roborev: Combined Review (
|
Resolve overlapping appearance settings changes so shared zoom and the new XML rendering preference remain available together.
roborev: Combined Review (
|
roborev: Combined Review (
|
|
looking |
Clients on different displays need independent zoom preferences. Use the configured zoom as a default and keep interface changes in local storage, removing the server write queue from zoom controls. Keep fixed overlay positions in viewport coordinates while scaling their contents with the interface. Document when config edits take effect.
roborev: Combined Review (
|
Appearance, the desktop status bar, and desktop shortcuts use one Zoom preference in place of the separate Text size and Desktop zoom controls. Existing local preferences migrate to it, and all controls use the same supported percentages.
The optional
zoom_levelinconfig.tomlsupplies a default for browsers and desktop webviews without a local preference. Interface changes stay in that client’s local storage, so clients with different displays keep independent choices. Manual config edits require a daemon restart and client reload; explicit settings API updates retain validated TOML persistence.Fixed typeahead menus, context menus, and chart tooltips keep their viewport positioning while their contents scale with the interface. The date picker retains its existing scale because the pinned component fixes its panel width. The pinned kit-ui integration and browser coverage are documented in
DESIGN.md.Closes #1697