Tracking issue for design/implementation changes needed to support lazy FCM subscriptions.
Lazy FCM subscriptions don't require the FCM messages to be delivered immediately if the the browser isn't in the foreground.
Instead they are queued and replayed next time the browser is foregrounded. This helps to avoid unnecessarily waking up the browser.
This is useful for Sync invalidation for example where frequent FCM messages are expected and it's not critical to process them right away if the browser isn't in the foreground.
Comment 1 by peter@chromium.org
, Sep 11