Yash, this is WAI right? I think we just expect the user to hit the home button if the experience fails to load.

This sounds a DD home bug. Normally, when device becomes offline, the tiles should be replaced by offline icons. And clicking on these icons is a noop.

We could detect this error case in Chrome though to be safe.

Even if we shouldn't get to this state if there is no network connectivity, we should still handle errors. Among other things, it could also happen that the specific site or resources are unavailable even though the network is connected.

I saw this issue was raised to P1, is this a release blocker?

Agreed that we should handle this.

Though, this doesn't sound like a blocker to me because as Michael pointed out, we expect the user to hit the home button to return to Daydream.

In any case, the server not reachable and other errors are probably more reasons to do this.

Issue 745863 has been merged into this issue.

 Issue 765775  is fixed in M63. What is the plan for this issue? is it something we'd merge back or fix in M64?

I don't think we should merge this back.

Perhaps we could show a toast after x = 10s that conveys "Oops something went wrong, going back to ...".

@gordonbrander, what do you think?

Per ymalik@, I think the right thing to do here would be to present a message informing the user that the content is slow and allowing the user to back out to DDH (same style we use for WebVR apps that don't submit frames).

Not presenting a message might cause confusion as to what happened, and the perception would likely be that this is a problem with Chrome/DD (it's not).

 Issue 817463  has been merged into this issue.

Ian, assigning this DLA bug to you, please re-assign as necessary :)

I think we need a mock or a string here Gordon. This also feels very low priority. I don't think users are likely going to run into this given the vetting of DLA content. The offline case is most concerning to me; do we have any idea of how frequently users use Daydream offline?