Matt Giuca

Hi, I'm the [Redditor who reported it](https://www.reddit.com/r/PWA/comments/julurq/ordinary_puzzles_a_progressive_web_app_puzzle/gcgnoai/?utm_source=reddit&utm_medium=web2x&context=3). I can give a bit more context. Chrome 86.0.4240.193 (Windows, Chrome OS, I tried both) I can trigger reliably: Just imagine that the...

To try and clarify this issue: it seems that you're not asking for a definitional change but an actual behavioural change to the Web-facing `URL` API. Specifically, the changes you...

Ohh, I see what you want now. (Tip: When filing a bug asking for a change to API behaviour, please give sample input and output so it's clear what you...

Yes, Chrome's current implementation on Windows would be able to support any symbols we want. It's more that if we, or any other browser, wants to implement the API using...

> I think I also raised this previously: while the promise to update the badge is held, we cam just return rejected promises. We then leave it to the UA...

> That's ok. It's an early incubation, so one should be using this in production so we are not breaking anyone. We (Chrome) are [about to ship the API to...

@cwilso : > Of course we would have concerns about compat-breaking changes of something we've shipped; that should never equate to "we will not ever make changes," only that we...

I am OK with the promise rejecting for "reasons"* if it's something that isn't going to work again after a retry. That means if the developer _really_ cares about whether...

OK great, I think we are all in agreement (mostly). I will send a PR to add this recommendation. I am happy if we add true (non-recoverable) failure conditions later....

You could perhaps do a more basic heuristic (without having to depend upon past history) which is checking whether the manifest filename has something that looks like a version in...