NTP should highlight offline enabled sites when offline |
|||||
Issue descriptionSites that we think might work offline should be shown first and highlighted. Sites that we know won't work should be shown disabled or hidden.
,
Sep 17
,
Sep 17
"might work offline" also includes sites/apps that have installed service workers that will interpret the request, and not produce 404s. In general, the user should not be surprised when they click on something in the NTP. If we present an enticing option that 404s because the user is offline, we are not doing the right thing. Whether we do that by greying out sites/links/articles that cannot be accessed when the user's device is currently offline, or badging, is a UX/product call (eg greying would not cause UI to move around). Bug 856420 is a related to this, but for omnibox suggestions.
,
Sep 17
iOS does not support service workers. Add iOS back if you believe we can help here.
,
Sep 18
I'm referring to the recent sites. Also this is relevant for desktop, so adding in labels for those. Currently 'might work offline' means (a) has a service worker and (b) the service worker has a fetch handler. That doesn't guarantee it will work offline but without this we can be sure it won't. I didn't realise we show an offline badge, I've never seen this. I don't think it exists on desktop.
,
Sep 18
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by s...@chromium.org
, Sep 17Labels: OS-Android OS-iOS