Organize settings into retained topic tabs
This commit is contained in:
@@ -0,0 +1,20 @@
|
||||
# Settings topic tabs
|
||||
|
||||
Settings opens on Appearance (animations and fonts), with Connection,
|
||||
Notifications, Tools (storage, health, library), and Updates alongside it.
|
||||
Material uses native horizontally scrollable tabs. Cupertino uses its native
|
||||
sliding segmented control inside a horizontal scroll view, so long labels and
|
||||
large accessibility text remain reachable on narrow screens.
|
||||
|
||||
Category navigation stays below the shell/navigation bar; each page scrolls
|
||||
beneath the category selector and retains its own position. Pages mount on
|
||||
first visit and remain mounted, preserving unsaved fields. Hidden pages have
|
||||
TickerMode disabled. Notification settings are not requested until the topic
|
||||
is first opened. The shared connection/controller still lives at screen scope.
|
||||
Cupertino's grouped background fills the entire page, including the top inset.
|
||||
|
||||
Checks: 144 settings and Settings-route application tests pass, including four
|
||||
new lazy/state/scroll/large-text category tests. Existing tests explicitly open
|
||||
Connection or Notifications before asserting their controls. Analyzer clean.
|
||||
Integrated preview and full-app browser captures are owned by the parent lane;
|
||||
this lane did not capture or deploy independently.
|
||||
Reference in New Issue
Block a user