I can't see anything in the commit history here @zachleat: https://github.com/google/WebFundamentals/commits/31bac6fa860e4415c7cc061a59bcc1dbe6045165/src/content/en/progressive-web-apps/_index.yaml … But I haven't looked through all the commits. It is mentioned here though:https://developers.google.com/web/ilt/pwa/introduction-to-progressive-web-app-architectures …
-
-
Replying to @TheRealNooshu @slightlylate
Ah, thank you! Very narrow use of the term there, hmm.
1 reply 0 retweets 0 likes -
-
Replying to @slightlylate @TheRealNooshu
Ah, interesting—so it needed to be verifiable in something like
@____lighthouse. (Thanks!)1 reply 0 retweets 0 likes -
Yeah; also, think games where the content is entirely in a `<canvas>`
1 reply 0 retweets 0 likes -
Oh, hmm—that suggests it was removed because it’s no longer endorsed rather than due to a technical limitation in automated testing.
1 reply 0 retweets 0 likes -
-
Hard argument to make that one should set rules that can't be enforced.
1 reply 0 retweets 0 likes -
Oh, for sure. I just remember the early guidelines on PWA including a formal endorsement of progressively enhanced content. Looks like there may be a definition disconnect—
1 reply 0 retweets 0 likes -
Replying to @zachleat @slightlylate and
I thought it endorsed progressively enhanced content when y’all are using a broader definition of progressive enhancement for specific PWA features.
1 reply 0 retweets 0 likes
Yeah, and we spent a lot of time discussing if/how we could test progressive enhancement at runtime (hard to do with high fidelity and low cost). Game corner-case was too gnarly.
-
-
Alright yeah that makes sense—thanks for the insight!
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.