Skip to content

fix(browser): native row and search styling in record lists #53

Closed

Description

@trmosala

What to build

The browser's record lists (history, downloads, passwords, bookmarks and contacts) look and respond like native lists. Rows have hover and focus surfaces, dividers use theme tokens, and search fields match the native list search field.

Acceptance criteria

  • Rows in every record list show hover and focus-visible surfaces that match native lists.
  • Row dividers use the themed weak border colour. No list falls back to the default border colour.
  • Each list's search field matches the native list search field, including background, radius, padding and search icon.
  • Keyboard navigation and row activation behave as before.
  • The classic-layout appearance is unchanged outside the record lists.
  • LTR and RTL both render correctly.
  • Scoped lint passes. Package typecheck passes where dependencies are installed.
  • Before/after screenshots are attached for each layout touched.

Blocked by

None - can start immediately.

Context

Source: browser panel native-styling audit, 2 October 2026. Coordinate with ongoing browser changes in #37–#48. Operation, busy, error and recovery states belong to #43 and are out of scope. Another agent owns the tab-strip alignment; do not restyle the strip in this slice.

Activity

  1. added
    bugSomething isn't working
    ready-for-agentScoped work with acceptance criteria and recorded blockers
    on Oct 2, 2026
  2. trmosala commented on Oct 2, 2026

    @trmosala
    OwnerAuthor

    Closing at the user's request after implementation and review.

    Record rows use native hover/focus surfaces and themed dividers. List searches use native metrics and leading search icons.

    Validation: 18 tests pass with 514 assertions; app package typecheck passes; scoped lint reports 0 errors and 25 warnings; formatting and diff checks pass. Mounted Chromium fixtures cover both layouts, light/dark themes and LTR/RTL. They do not verify native Electron corners.

    Implementation remains uncommitted in the isolated browser-gaps worktree. Closure records completion of the local implementation, not a merge or release.

    Full screenshot and validation archive

    classic, light, ltr

    Before

    Before: history, classic, light, ltr

    After

    After: history, classic, light, ltr

    classic, dark, rtl

    Before

    Before: history, classic, dark, rtl

    After

    After: history, classic, dark, rtl

    new, light, ltr

    Before

    Before: history, new, light, ltr

    After

    After: history, new, light, ltr

    new, dark, rtl

    Before

    Before: history, new, dark, rtl

    After

    After: history, new, dark, rtl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingready-for-agentScoped work with acceptance criteria and recorded blockers

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions