Wil Clouser [:clouserw] Reporter
	Description • 10 years ago

Sometimes the loading screen for the Marketplace just spins.  We should be able to recognize a broken situation and try to fix it.  A good first start would be a loader timeout that:

* Verifies they are online (this should have already happened by now)
* clears their localStorage
* clears their local offline cache
* resets any region/carrier overrides
* logs everything it is doing and why
* reloads the page

	Andy McKay
	Comment 2 • 10 years ago

The one that concerns me more is when you end up with a blue x in the top left hand corner and nothing else. Is that something we can deal with in this, or is it a failure of our code to even load?

	Mathieu Pillard [:mat]
	Comment 3 • 10 years ago

The blue X in the top left corner is a failure of (usually all) our static assets to load. Even if we could detect it by somehow hacking around the HTML, we don't know what causes it, so we don't know what we could do in this situation...

	Christopher Van Wiemeersch [:cvan]
	Comment 4 • 10 years ago

(In reply to Mathieu Pillard [:mat] from comment #3)
> The blue X in the top left corner is a failure of (usually all) our static
> assets to load. Even if we could detect it by somehow hacking around the
> HTML, we don't know what causes it, so we don't know what we could do in
> this situation...

We could/should include some JS in the package (damn CSP disallowing inline scripts) that uses the Resource Timing API to record if/when resources load and if they fail, report it to some service like Ashes/New Relic/Sentry. If we can get numbers on how often this happens, that would help us better assess what's going on.

	David Durst [:ddurst]
	Comment 5 • 9 years ago

This is an interesting problem, with no clear solution. Rearchitecting the loading of Marketplace and assets *could* help address it, but... short of a major overhaul, this is not going to get addressed.