Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
samizdat
samizdat
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 32
    • Issues 32
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Michał "rysiek" Woźniak
  • samizdatsamizdat
  • Issues
  • #51

Closed
Open
Opened Jul 08, 2020 by Michał "rysiek" Woźniak@rysiek🔒Maintainer

ServiceWorker not kicking in on force-reload

Relevant:

  • https://stackoverflow.com/questions/37559415/how-to-make-serviceworker-survive-cache-reset-shiftf5
  • https://developers.google.com/web/fundamentals/primers/service-workers/lifecycle#shift-reload

Might require a simple FAQ entry. Unless we want to muck around with how force-reload is handled.

Edited Sep 08, 2020 by Michał "rysiek" Woźniak
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: rysiek/samizdat#51