▲ 68 ▼ Mozilla does not want to support PWAs in Firefox, yet MDN has a PWA manifest and can be installed in Chromium. (discuss.tchncs.de) submitted 3 years ago by decodehug647@discuss.tchncs.de to c/firefox@lemmy.ml 32 comments fedilink hide all child comments
[–] Vent@lemm.ee 4 points 3 years ago (1 child) Real PWAs, though PWAs aren't that different from shortcuts tbh permalink fedilink source parent hideshow 2 child comments replies: [–] gamey@feddit.rocks 2 points 3 years ago (1 child) As far as I know their main purpose is to cache various parts of the website properly which is a lot more than just a shortcut. permalink fedilink source parent hideshow 2 child comments replies: [–] lemann@lemmy.one 3 points 3 years ago (1 child) Regular websites can do that too using service workers - Lemmy's webapp uses this to show an error when an instance is unreachable What we call a PWA is usually just a webpage with a webmanifest, and a service worker script to manage loading those cached resources you mentioned permalink fedilink source parent hideshow 2 child comments replies: [–] gamey@feddit.rocks 2 points 3 years ago Seems like you are right, the caching for proper offline usage and use with very limited internet connections is all done trough service workers. Their main job seems to be system integration and while Firefox Android kind of sucks at that too it doesn't seem like they ever cut that down so they just dropped it for desktop users. permalink fedilink source parent
[–] gamey@feddit.rocks 2 points 3 years ago (1 child) As far as I know their main purpose is to cache various parts of the website properly which is a lot more than just a shortcut. permalink fedilink source parent hideshow 2 child comments replies: [–] lemann@lemmy.one 3 points 3 years ago (1 child) Regular websites can do that too using service workers - Lemmy's webapp uses this to show an error when an instance is unreachable What we call a PWA is usually just a webpage with a webmanifest, and a service worker script to manage loading those cached resources you mentioned permalink fedilink source parent hideshow 2 child comments replies: [–] gamey@feddit.rocks 2 points 3 years ago Seems like you are right, the caching for proper offline usage and use with very limited internet connections is all done trough service workers. Their main job seems to be system integration and while Firefox Android kind of sucks at that too it doesn't seem like they ever cut that down so they just dropped it for desktop users. permalink fedilink source parent
[–] lemann@lemmy.one 3 points 3 years ago (1 child) Regular websites can do that too using service workers - Lemmy's webapp uses this to show an error when an instance is unreachable What we call a PWA is usually just a webpage with a webmanifest, and a service worker script to manage loading those cached resources you mentioned permalink fedilink source parent hideshow 2 child comments replies: [–] gamey@feddit.rocks 2 points 3 years ago Seems like you are right, the caching for proper offline usage and use with very limited internet connections is all done trough service workers. Their main job seems to be system integration and while Firefox Android kind of sucks at that too it doesn't seem like they ever cut that down so they just dropped it for desktop users. permalink fedilink source parent
[–] gamey@feddit.rocks 2 points 3 years ago Seems like you are right, the caching for proper offline usage and use with very limited internet connections is all done trough service workers. Their main job seems to be system integration and while Firefox Android kind of sucks at that too it doesn't seem like they ever cut that down so they just dropped it for desktop users. permalink fedilink source parent