Repository navigation
plugin-list: the list toolbar Print button is a bare window.print() — no preview, no output, silent no-op in headless/WebView #4462
Description
Reported from an app project (steedos-labs/os-project-titanwind-ehr#1161) on @objectstack/*@17.0.0-rc.6.
What it does
The list view toolbar's Print button is a bare browser print call:
// packages/plugin-list/src/ListView.tsx:2626
onClick={() => window.print()}No print layout, no preview, no PDF generation, no downloaded artifact. The same bare
call also backs packages/plugin-report/src/ReportViewer.tsx:115 and
packages/app-shell/src/views/DashboardView.tsx:101.
Why it's a defect, not just a thin feature
window.print() is a no-op in exactly the environments a platform gets driven in:
headless/automated browsers and several embedded WebViews. The click resolves normally —
no exception, no console error, nothing rendered. Observed at the reporting project:
the click dispatched successfully, console clean, nothing happened. From the outside it
is indistinguishable from a broken button, and it is being read by acceptance testers as
the product's "export to PDF" entry point.
Even in a normal desktop browser the result is the browser's own dialog printing the
whole Console chrome — unpaginated, tables clipped, styling unsuited to paper (this is
the exact workaround objectstack-ai/objectstack#1301 already documented and rejected as
inadequate).
Repro
- Open any object list view in Console.
- Click Print in the toolbar.
- Headless/WebView: nothing happens, no error. Desktop browser: the browser's print
dialog for the whole page, including Console chrome.
What we're asking for
Note that the real feature — a print/PDF primitive — was closed NOT_PLANNED as
objectstack-ai/objectstack#1301, so we are not re-litigating that here. Given that
decision, the minimum fix is to stop the button from reading as an export entry point.
In descending order of preference:
- Give the list a print stylesheet / print-scoped render so
window.print()produces a
usable page (no Console chrome, paginated, table not clipped). - Document the button's semantics explicitly ("opens your browser's print dialog"; not a
PDF export), so it stops being accepted against "export PDF" requirements. - Failing both, remove or gate the button rather than ship a control that is a silent
no-op in a supported runtime.
Related
objectstack-ai/objectstack#1301— print / PDF export, closed NOT_PLANNED- Spec-side twin (
exportOptionscontract mismatch): spec:ListView.exportOptionsis typed as a bare array, but the only renderer readsexportOptions.formatsobjectstack#8010 - Project-side evidence: https://github.com/steedos-labs/os-project-titanwind-ehr/issues/1161#issuecomment-5265108797
Activity
yinlianghui commentedon Aug 12, 2026
CLAIM — session
session_017Qqyix2QcnpUC9XeYVDzx3, branchclaude/issue-4462-print-usable-page.Ruling (delegated authority; open veto window): option 1 + option 2 as a rider; no removal, no headless gating. objectstack#1301 (real PDF primitive) is closed NOT_PLANNED and is not re-litigated; within that constraint:
window.print()produce a usable page via a shared@media printstylesheet at the level where the console chrome lives (app-shell global styles — one mechanism, so the same rules serve list, report, and dashboard): hide the shell chrome (nav/header/toolbars) under print; let the active content area print full-width; list table unclipped and paginating (overflow: visible, sensiblebreak-insiderules). Plugin-list gets its own print rules only if the shared sheet measurably can't reach something.Red-first honesty:
@media printis not executable in jsdom/happy-dom — pin what IS assertable (the stylesheet ships and contains the chrome-hiding selectors; the buttons carry the new tooltip key through the i18n channel; defaults-map rows exist) and state in-file what cannot red in vitest, the PR #4480 pattern. Do NOT claim a rendered-print pin that cannot fail. Verify the actual print rendering once by browser print-preview screenshot if the environment allows (skillobjectui-4462:verifymay help); if not, say so.Grading: patch per touched package (
@object-ui/plugin-list,@object-ui/plugin-report,@object-ui/app-shell) — CSS/tooltip only,.d.ts-checked, never major.Surface (mutual exclusion): app-shell global stylesheet + the three named button sites + i18n defaults-maps + tests + changesets. ⛔ Do NOT touch
app-shell/src/views/ObjectView.tsx(#4463 in flight), the app-surface/landing components (#4473 in flight),console/organizations/manage/**(#4480 armed),plugin-calendar(#4452 in flight), or the DOM-leak ledger. If the shared sheet's natural home collides with an in-flight file, report instead of editing.Generated by Claude Code
Generated by Claude Code
fix(print): window.print() produces a usable page and the Print butto…