Files
pad/web
xarmian 74589e98bb fix(attachments): make the live chip a button, not a link (TASK-2424)
From the orchestrator's pass on TASK-2424. The chip opens the options
panel — it does not navigate — but it was still an <a href download> that
only intercepted primary click. Middle-click and aux-click therefore
opened or downloaded the file straight past the panel, which is the exact
accidental download the panel exists to prevent, and screen readers
announced a link for a control that opens a menu.

A button has no URL to activate, so the bypass cannot exist rather than
being intercepted, and it matches the strip's file tile — the same
control, now with the same semantics. renderHTML stays an <a download>:
that is the clipboard / read-only shape, where a link is honest and there
is no panel to open.

Deleted chips now use `disabled` rather than a dropped href: a disabled
button receives no click or keydown at all, where the anchor's handlers
still ran and had to swallow events. It is also blurred explicitly first,
since a chip the user is focused on when another surface deletes the row
would otherwise strand focus on an inert element. The keydown suppression
moved ahead of the deleted bail so a stray Enter can never reach
ProseMirror's keymap and split the paragraph the chip sits in.

.file-chip carries the button reset explicitly (font: inherit), since the
UA's 13.33px Arial would otherwise shrink the live chip away from the
read-only one.
2026-08-04 13:09:07 +00:00
..
2026-03-26 01:52:36 +00:00
2026-03-26 01:52:36 +00:00
2026-03-26 01:52:36 +00:00
2026-03-26 01:52:36 +00:00
2026-03-26 01:52:36 +00:00

Pad Web UI

SvelteKit 2 + Svelte 5 frontend for Pad, compiled to static files and embedded into the Go binary.

Development

npm install
npm run dev          # Dev server at localhost:5173 (proxies API to localhost:7777)
npm run build        # Production build to build/
npm run check        # Type checking with svelte-check

When developing, run the Go backend separately with make dev from the project root.

Building for Production

Do not build in isolation. Always use make build from the project root — this builds the web frontend, then compiles the Go binary with the build output embedded via //go:embed.

Stack

  • Svelte 5 with runes ($state, $derived, $effect)
  • SvelteKit 2 with adapter-static (SPA mode)
  • Tiptap block editor with markdown round-trip
  • svelte-dnd-action for drag-and-drop in board/list views
  • SSE for real-time updates
  • TypeScript throughout

Structure

src/
  routes/                    SvelteKit pages
    +layout.svelte           App shell (sidebar + main)
    +page.svelte             Landing/redirect
    [workspace]/
      +page.svelte           Dashboard (collections, phases, activity)
      +layout.svelte         SSE connection per workspace
      [collection]/
        +page.svelte         Collection view (board/list)
      [collection]/[item]/
        +page.svelte         Item detail + editor
      conventions/            Purpose-built conventions page
      playbooks/              Purpose-built playbooks page
      settings/               Workspace settings
  lib/
    api/client.ts            HTTP API client
    components/
      layout/                Sidebar, navigation
      editor/                Tiptap editor, raw markdown editor
      fields/                FieldEditor, relation picker
      items/                 ItemCard, ItemDetail
      collections/           BoardView, ListView
      common/                StatusBadge, badges, modals
      search/                CommandPalette
      activity/              ActivityFeed
    stores/                  Svelte 5 reactive stores
      workspace.svelte.ts    Workspace state
      collections.svelte.ts  Collection + item state
      ui.svelte.ts           Sidebar, mobile state
    types/index.ts           TypeScript types and constants
  app.css                    Global styles and design tokens