Library Affected:
workbox-build

We don't have any prominently featured "real world" examples of using generateSW with runtimeCaching to produce a service worker that is focused on runtime caching.

The documentation for the feature, at https://developers.google.com/web/tools/workbox/reference-docs/latest/module-workbox-build#.RuntimeCachingEntry, is rather buried.

This is relate

The documentation doesn't mention a way to change the name of the generated file.

It does mention gulp, but I am using Angular 4's angular-cli to generate my assets and then run sw-precache separately to generate the service worker.

the packages.json file consists of this command:
"sw": "sw-precache --config=sw-precache-config.js --verbose"

And the sw-precache-config.js file has the

As caught by @OliverJAsh:
Hey! The fixed background is causing the whole page to be repainted on scroll, FYI

Are you aware of any different behavior when a PWA (using offline-plugin) is added to the home screen using "Add to Home Screen" on Chrome/Android or Safari/iOS?

I'm having problems with the app getting stuck using the cached version when it was installed and never updating.
I even have offline-plugin responseStrategy set to network-first but it seems to always use the cached version after add

Hello guys

I just came from the npm swToolBox page & the links for the API & HTML docs are broken!

Ex: the Bolded/italized text has the issue

Use the toolbox
To understand how to use the toolbox read the Usage and API documentation.

As PWA add to home screen workflow is different on each platform/browsers, we could add a button on the interface to trigger the installation. It will standardize add to home screen workflow for all browsers.

See official doc
for more informations

This project is using sw-precache instead of the latest @angular/service-worker and ng-pwa-tools.

At Google I/O last week, they announced that https://github.com/GoogleChrome/workbox would be the preferred option over sw-precache going forward.

However, Angular seems to be creating a better integrated SW and PWA story using the tools mentioned above. That said, it would be interesting to

According to the spec, Client is not a child of the EventTarget class.

Also the Notification class is a child of the EventTarget class.

FWIW TypeScript agrees with what is in the spec. I'd be happy to supply a PR wi

if you modify the swDest option to generate the serviceworker in other path, this not affect the path to generate the development service-worker.

I need to see the code to fix this, but would be nice to have this in the documentation.
this is the fix to generate serviceworker in development in the right path.

  dontAutoRegisterSw: true,
  devSwSrc: {
    from: './public/sw-dev.js'

Environment

• Browser: Chrome
• Version of service-mocker: 2.1.2

Expected Behavior

The hash of a URL should not be part of the url when processing.

Current Behavior

Hash is a part of the url when processing.

When browsers send an HTTP request they omit the hash part of the URL.
It appears that the fetch event sends the Request object with the url as is, no modificati

Mobile Era is using room names as tags. Room UX should be improved. On mobile they should be listed on cards and they should be filterable.

Some accessibility issues to fix:

• HTML more semantic in order to represent the information. For example, my opinion is the future weather should be a table, and the information of the current day should have a definition list.
• Hide the dialog if is not visible.
• Use alternate texts for the icons.

The landing page should be served over planktos if the browser supports it. Also a live demo section should be added that informs the viewer that the page was downloaded from peers.

The Lighthouse PWA audit flags a Web App Manifest that:

1. Is lacking an icon.
2. Has an icon that is less than 512px square.
3. Is not a PNG.

These requirements should be enforced in the Customizer when selecting a site icon, and/or a warning notice should be shown with the Customizer control when the selected icon does not satisfy the requirements. This should also be added as a Site He

Describe the bug
Checkout button doesn't redirect to checkout page

To Reproduce
Steps to reproduce the behavior:

1. Select product
2. Select variations
3. Click in checkout button
4. Redirect to homepage

Expected behavior
Redirect to ckeckout page

Screenshots
If applicable, add screenshots to help explain your problem.

**Smartphone (please complete the following