-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Closed
Copy link
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)e: flutter.jsIssues with Flutter web custom initialization through JS APIsIssues with Flutter web custom initialization through JS APIsfound in release: 3.3Found to occur in 3.3Found to occur in 3.3found in release: 3.6Found to occur in 3.6Found to occur in 3.6has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyWeb applications specificallyr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer versiontoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Description
Hello, I'm working on a project that is performance-sensitive, I need to squeeze every available resource in the HTML5 world to enhance performance and loading times.
Flutter apps download assets again in the second visit despite service worker, I know this happens because there is no call to
self.clients.claim();
Is there a reason why self.clients.claim() is not being called? Imo this is a desirable behavior by default or at least it should be a feature you can enable via environment.defines
Steps to Reproduce
- create a new project
flutter create example - build it for the web
flutter build web - serve it
python3 -m http.server - load the app for the first time
- reload the app and notice how assets added by the app developer are downloaded again
Expected results: service worker should kick in right away
Actual results: service worker start caching things after the second session
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)e: flutter.jsIssues with Flutter web custom initialization through JS APIsIssues with Flutter web custom initialization through JS APIsfound in release: 3.3Found to occur in 3.3Found to occur in 3.3found in release: 3.6Found to occur in 3.6Found to occur in 3.6has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyWeb applications specificallyr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer versiontoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.