You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now (on Firefox and Chrome, at least) any image, icon and badge URL passed into showNotification() goes straight to the remote URL. It would be a much better experience if those requests were routed through the fetch event, so that we could use cached assets instead.
There is a work-around using cache.match() -> res.blob() -> FileReader.readAsDataURL(), but it's pretty inefficient since the lack of URL.createObjectURL (as removed in #688) means that every image is turned into a base-64 encoded string. Since the introduction of the image attribute, some of these images can be pretty huge.
The text was updated successfully, but these errors were encountered:
Right now (on Firefox and Chrome, at least) any
image
,icon
andbadge
URL passed into showNotification() goes straight to the remote URL. It would be a much better experience if those requests were routed through the fetch event, so that we could use cached assets instead.There is a work-around using
cache.match()
->res.blob()
->FileReader.readAsDataURL()
, but it's pretty inefficient since the lack ofURL.createObjectURL
(as removed in #688) means that every image is turned into a base-64 encoded string. Since the introduction of theimage
attribute, some of these images can be pretty huge.The text was updated successfully, but these errors were encountered: