Skip to content

ui: Polish the tab strip, new-tab page, Settings, Visibility table and Overview - #59

Open
snowopsdev wants to merge 25 commits into
mainfrom
feat/ui-polish-2
Open

snowopsdev wants to merge 25 commits into
mainfrom
feat/ui-polish-2

Conversation

@snowopsdev

Copy link
Copy Markdown
Member

A round of UI polish on five spots that felt unfinished:

  • New tab button: the + sat after the address bar instead of next to the tabs.
  • Narrow windows: a tab shrank to "C.." while the address bar kept its width.
  • New-tab page: it said "Search or enter address" twice and had no search box.
  • Settings: led with two sections that only say "not configured in this build".
  • SEO panels: the Visibility table scrolled about 1,000px sideways, and Overview's scores and counts were loose cards.

The new-tab page: + beside the tab, a search field, the aligned checklist

What changes for a user

  • Tabs:
      • follows the last tab and stays in view when the tabs scroll.
    • In the narrowest window (664px) the active tab keeps 122px, so "New Tab" or a short title is whole. The address bar gives way to 202px, still enough for a host like en.wikipedia.org.
    • Narrowing the window brings a cut-off active tab back into view.
  • New-tab page:
    • A centred search field replaces the repeated tagline. It shares the address bar's code, so what you type is handled exactly as in the address bar. A new tab still focuses the address bar.
    • The getting-started checklist's buttons line up in one column, with a progress bar that fills from the left.
    • The "Connect Search Console" item is left out when the build has no Search Console.
  • Settings:
    • Account and Search Console are left out when the build has no service for them; the gear then opens at the top of the sheet (Data sources).
    • The section list highlights the section you've scrolled to.
    • A data provider that isn't available yet is one line.
    • History retention is one row of four buttons.
    • Telemetry's "no endpoint" notes are muted text instead of amber warnings.
  • Visibility: each crawler is a button, marked when it sees the page differently from the browser and with how many facts differ. One three-column table compares the chosen crawler with the browser, and it opens on the first crawler that differs. Nothing scrolls sideways at any panel width.
  • Overview: the health score, the AI-readiness score, the error/warning/notice counts and "Highlight everything" sit in one card. The rings stay beside their text in narrow panels instead of stacking, so Top issues starts about 80px higher.

Things to know

  • Keyboard order: Tab now reaches + between the tabs and the address bar, matching where it sits.
  • Every screenshot baseline is regenerated. All 92 come from Linux CI run 44583152843, where every other Linux e2e test passed.
  • Follow-ups left open:
    • The command palette, if opened in the first moment after launch, can keep offering "Search Console settings". Picking it opens Settings at the top.
    • A source-text layout guard in chrome-grid-styles.test.ts is brittle.
    • One Settings scroll ordering is covered only by its mirror case.

The decisions and the alternatives rejected for each item are in the .feature.md files: tabs, browser-polish, help, account-settings, data-sources, serp-panels, seo-sidebar and design-tokens.

Reviewed with sol-loop: 3 rounds with gpt-6.2-sol on high. Sol verdict: approved

Created with Claude Fable 5.2 and Claude Opus 5.5 (the four lanes) in Claude Code, reviewed by GPT-6.2 Sol.

🤖 Generated with Claude Code

snowopsdev and others added 25 commits November 19, 2026 11:15
… width at the minimum

CHROME_ROW puts new-tab right after the tablist (its next sibling, never in its
scroller). ACTIVE_TAB_MIN_WIDTH_PX (132) keeps the active tab's label readable;
ADDRESS_MIN_WIDTH_PX goes 240 -> 192 so CHROME_MIN_CONTENT_WIDTH_PX stays 664.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…an aligned checklist with a meter

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…croll, and compacts gated data sources and retention

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rview's summary is one card

The probe table's eight columns scrolled about 1,000px sideways in the panel at every width: chips
choose a crawler (those that differ marked with their counts) and a three-column table compares it
with the browser. Overview's scores, counts and Highlight everything become one summary card whose
rings stay beside their words under the panel's minimum. Closes the Visibility table's Left-for-later
item and adds its parts to NARROW_PANEL_FITS; NARROW_PANEL_WRAPS shrinks Overview's rings instead of
stacking them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ar, tighter gaps

NEW_TAB_LABEL is 52px and a typical scheme and host 140-157px of --text-body:
the label sits --space-1 from its x and the address text --space-2 from its
badge, so both fit the 332px the window's minimum leaves. TYPICAL_ORIGIN is
the yardstick; the minimum stays 664 (NARROW_WINDOW derives from it).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…llows the scroll, gated data sources are one line, retention is a segmented control

Account and Search Console are left out once main says this build has no
service for them, and a request for either lands on the top of the sheet.
The section list marks the section in view as the content scrolls. A data
source whose legal gate is closed is a single line with its reason. History
retention is one row with a segmented radio group. Telemetry's no-endpoint
note is muted text.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…an aligned checklist with a meter

The start view's search field and the address bar share useAddressInput (the reducer, Enter/Escape/blur,
browser.navigate as typed); the address bar keeps the new tab's focus. ADDRESS_PROMPT is the one wording.
The checklist's rows are one subgrid (actions share a column and its width), stacked under the labels in
a card under SETUP_CHECKLIST_COLUMNS_MIN_PX; a decorative per-item meter; Hide is a quiet chip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e tab readable

The + is the tablist's next sibling: right after the last tab, pinned at the
tablist's end once it scrolls, 4px from the tabs and 8px from the address bar.
The active tab keeps --active-tab-room (122px at the window's minimum, never
under --tab-min) and the address bar gives way only to 202px; below the
minimum the active tab gives way first, so the row stays whole down to 448px.
The tab's label sits --space-1 from its x and the address text --space-2
from its badge, which the minimums count on.

Tests: chrome-grid-styles (new-tab-follows-the-tablist, the new variables and
gaps), boot (minimum from ACTIVE_TAB_MIN_WIDTH_PX), a jsdom chrome-row-dom-order
test, and tabs.e2e (new-tab-button-follows-the-last-tab,
narrow-row-shares-room-with-one-tab, the new Tab order and widths).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…at 300, 360 and 664px, and Overview's summary card

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… summary is one card

The probe table is chips and a three-column comparison that never scrolls sideways; canonical and
robots.txt URLs wrap instead of being cut. Overview's health score, AI-readiness tile, counts and
Highlight everything share one card, the rings 64px beside their words (48px under the panel's
minimum, where they used to stack). The spec takes the header padding and URL wrapping found when
looking at the 300px panel, and the measured position of Top issues.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… per item done

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
N items done fill the meter's first N segments, whichever items they are, so it reads as progress
rather than showing gaps (items 4 and 5 done lit only the last two segments).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…h Console item without a client

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…out a client

Settings now leaves the Search Console section out in such a build, so the item's button opened
Settings on Data sources. Progress, the meter and the all-done check count the items listed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the tabs, new-tab search, Settings, Visibility and Overview

Actuals from probe run 44583152843 (baselines removed; every other Linux e2e passed).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cuts it

Resizing from 1280px to the 664px minimum left the strip scrolled to the first tab, so a third
active tab was out of view until it changed or took focus. A tab the user scrolled away stays put.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…eaves or the content resizes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…es or the content resizes

A late gsc.watch answer that left Search Console out while it was the section in view left the list
with no aria-current until the next scroll. A section asked for that is still shown stays current.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ling the active tab away

Scroll events run before resize observations, so the strip's clamped scroll on narrowing marked the
active tab as already cut and the resize left it out of view (seen when the tabs e2e ran after others).
Escape's select() in the address field also only runs while that field still has focus.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Leaving Search Console out (or the sheet growing) shortened the content and clamped its scroll; that
scroll event released the pin, so a requested Telemetry gave way to History with no user input. A
scroll that moves up onto the content's end is the layout's: it moves the pin instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-19T18:28:05.193696Z 2b7f52f PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant