Skip to content

t27os: browser page chrome on the home's matte glass - one navigation bar, no stacked plates #14043

Closed

Description

@gHashTag

The browser page on domain tab B (baseline in PR 14042, issue 14037) does not look like the rest of the window. Measured in the code: the home fills the content area with the SURF_CONTENT tint once, and the browser page then draws a second full-pane tile plate over it plus a plate under the header and one under each button. The tints stack, so the pane reads as a dark opaque slab instead of the matte glass of the home. The header also shows a debug chip (cdp port, action word, pid).

The reference is the home page: one content tint, plain header text, a hairline, light pills for hover. The browser page must use the same ground and the same inks, with one compact navigation bar (back, forward, reload, address) and no diagnostics in the main view. The web page frame itself is not tinted or blurred.

Out of scope here: typing into the address field (14038), pointer and keyboard forwarding (14039), the CDP transport (14040), the agent command and step log (14041). This issue changes drawing only; the button rects stay the one source for both drawing and hit testing.

Order: lands after 14037.

Boundary

  • specs/t27os/glass_window.t27 :: fn draw_browser_page
  • specs/t27os/glass_window.t27 :: fn br_addr_rect

User Scenarios

  • Given the window in the Dark theme on glass, when the owner opens tab B before the first frame lands, then the page area shows the same matte glass as the home, with one navigation bar and a centred waiting line.
  • Given a live frame, when the owner looks at the page, then the frame is drawn untinted below the bar and the address is readable in the address field.
  • Given the pointer over a navigation button, when the frame is drawn, then that button shows the same hover pill the sidebar rows use.

Requirements

  • FR-001: draw_browser_page MUST NOT draw a tile plate over the whole pane, under the header or under a button.
  • FR-002: the navigation bar MUST hold back, forward, reload and one address field in a single row, with the address field rect given by one function used by the draw.
  • FR-003: the header MUST NOT show the cdp port, the action word or the pid.
  • FR-004: the button rects of br_btn_rect MUST stay unchanged, so br_btn_hit answers as before.
  • FR-005: the four theme states (window Dark, window Light, full-screen Light, full-screen Dark) MUST keep their grounds; this change adds no ground of its own.

Success Criteria

  • 0 calls of plate( inside draw_browser_page.
  • 0 occurrences of the debug chip text cdp : in draw_browser_page.
  • The spec tests of glass_window pass: exit 0.
  • 4 screenshots of tab B (one per theme state) and 1 of the home at the same window size are attached to the PR.

Activity

  1. gHashTag commented on Nov 16, 2026

    @gHashTag
    CollaboratorAuthor

    Ledger note on the hairline under the browser navigation bar (2026-11-16).

    • Was it agreed: partly. This issue names "a hairline" only in the description of the reference look (the home page: one content tint, plain header text, a hairline, light pills for hover). None of FR-001..FR-005 or the Success Criteria requires a hairline under the navigation bar.
    • Where it was implemented: PR t27os: browser page chrome on the home's matte glass (Closes #14043) #14044 (closed, superseded), commit 8325c09, in draw_browser_page: a HAIR (0.5 pt) fill at br_strip_bottom(y0) in THV_LINE_WHITE.
    • State on master 46d143c (build b8342, seen on screen): the window header keeps its hairline; the browser page draws no line between the address bar and the page frame. The Logs panel below the page keeps its own hairline on top.
    • Decision: not revived from t27os: browser page chrome on the home's matte glass (Closes #14043) #14044. If the owner wants the line, it is a two-line change in draw_browser_page with one test, in its own PR.

    Refs #14043

  2. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Spec created: specs/t27os/browser_chrome.t27 (typecheck OK, 1 test passes).

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions