GoogleChromeLabs / GoogleChromeLabs/squoosh
[offline/SW] "ready to work offline" message appears too early
Open
feature request
- Dominant language
- TypeScript
- Stars
- 25.9k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
We show it on the initial screen, but we haven't cached the codecs yet. We should probably show this message once the codecs are cached.
Contributor guide
Research direction
Start by tracing the initial screen and the codec-caching flow described in the issue. Change the readiness message timing so it appears only after the codecs are cached, then verify that it is absent on the initial screen and present once caching completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100