[web] make the search entry page usable #191

2026-11-04T15:54:07Z

eleith-gitea-agent Bot commented

2026-11-04 15:54:07 +00:00

Summary

Give unfiltered /search visits a usable search panel instead of an unrelated pieces listing, without querying or hydrating pieces until a keyword, type, or date filter is supplied.
Share the existing keyword/type/date controls between that panel and the navbar dialog. Keep dialog drafts across closing/reopening, scoped control IDs, a visible query focus indicator, and native GET field structure.
Keep filtered pages results-only with summaries and pagination; fresh submissions clear stale pagination. Native HTTP coverage checks that independent type/date filters actually return matching pieces.

Scope

Navbar loading is unchanged from main, including its existing after-load/idle preparation and normal /search fallback link. There is no Vite SSR conditional or CSS-loading workaround. This PR makes no PageSpeed or CSS-deferral claim; broader main-content rendering performance is separate follow-up work.

Verification

Web tests: 2,135 passed across 127 files.
Production-build native HTTP tests: 63 passed across two suites.
Svelte check: zero errors and warnings.
Web lint, production build, and whitespace checks passed.
Dedicated correctness, readability, and test reviews completed; the filter-only result coverage finding was fixed and its follow-up review is clear.

The SSR/native HTTP harness verifies rendered markup, route results, and native GET field structure. It does not automate browser focus, interactive widgets, enhanced navigation/error handling, or dialog draft persistence across reopening. No new PageSpeed benchmark was run.

## Summary - Give unfiltered `/search` visits a usable search panel instead of an unrelated pieces listing, without querying or hydrating pieces until a keyword, type, or date filter is supplied. - Share the existing keyword/type/date controls between that panel and the navbar dialog. Keep dialog drafts across closing/reopening, scoped control IDs, a visible query focus indicator, and native GET field structure. - Keep filtered pages results-only with summaries and pagination; fresh submissions clear stale pagination. Native HTTP coverage checks that independent type/date filters actually return matching pieces. ## Scope Navbar loading is unchanged from `main`, including its existing after-load/idle preparation and normal `/search` fallback link. There is no Vite SSR conditional or CSS-loading workaround. This PR makes no PageSpeed or CSS-deferral claim; broader main-content rendering performance is separate follow-up work. ## Verification - Web tests: **2,135 passed** across 127 files. - Production-build native HTTP tests: **63 passed** across two suites. - Svelte check: **zero errors and warnings**. - Web lint, production build, and whitespace checks passed. - Dedicated correctness, readability, and test reviews completed; the filter-only result coverage finding was fixed and its follow-up review is clear. The SSR/native HTTP harness verifies rendered markup, route results, and native GET field structure. It does not automate browser focus, interactive widgets, enhanced navigation/error handling, or dialog draft persistence across reopening. No new PageSpeed benchmark was run.

eleith-gitea-agent Bot added 1 commit 2026-11-04 15:54:07 +00:00

[web] make the search entry page usable

ci/woodpecker/pr/web Pipeline was successful

Details

ci/woodpecker/push/web Pipeline was successful

Details

e730e6f9be

eleith merged commit e730e6f9be into main

2026-11-04 15:58:57 +00:00

eleith deleted branch fix/deferred-search-and-search-page

2026-11-04 15:58:57 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: eleith/luzzle#191