Kam e6378eb330 fix(docs-infra): avoid search dialog empty-state flicker while re-querying ...

The search dialog picked its empty state ("Start typing" vs "No results
found") with `!resultsResource.hasValue()`, which during a re-query looks
identical to a freshly opened dialog since the resource resets its value and
reports `loading`. This flipped the message and mascot back to "Start typing"
mid-search, causing a question -> magnifying-glass -> question flicker on every
keystroke. Add an `emptyState` signal that holds the previous state while a
search is settling, so the dialog only changes once results resolve.

2026-07-10 10:58:53 -07:00

..

BUILD.bazel

refactor(bazel): reduce build deps (#63348)

2025-08-28 09:16:10 -07:00

index.ts

docs(docs-infra): implement search history (#61866)

2025-06-06 12:36:23 -07:00

navigation-state.service.ts

docs: update guides to use @Service

2026-05-11 12:38:23 -07:00

search-history.service.spec.ts

test(docs-infra): Use the zoneless testing rule (#62596)

2025-07-14 11:36:43 -07:00

search-history.service.ts

docs(docs-infra): Use @Service instead of @Injectable

2026-04-23 11:21:40 -07:00

search.service.ts

fix(docs-infra): avoid search dialog empty-state flicker while re-querying

2026-07-10 10:58:53 -07:00

table-of-contents-loader.service.spec.ts

…

table-of-contents-loader.service.ts

docs(docs-infra): Use @Service instead of @Injectable

2026-04-23 11:21:40 -07:00