So I think that you're experiencing a thing that I put in to try and not be a jerk to mobile users. On mobile devices, the log viewer loads the first set of logs, but defaults "automatic loading" to OFF so that huge logs don't tear through mobile data. If you click the "play" button in the upper-left, this should load the remaining logs.

It seems to load now, thanks. I'd be surprised if the number of people who click a logdog link but then don't want to see the contents is greater than 0 though -- did anyone ask for that?

Nope, just something I thought would be a good idea. "See the contents" isn't really prevented here - just burst loading of hundreds of megabytes by default. In this mode, you can scroll around, iteratively load logs, load the tail log and work from the bottom, or load the full log. The mobile mode just asks you to state your intent rather than presuming it.

In a way that I didn't understand and that slowed .e down enough that I bothered to file a bug :-)

I don't know of any other webapp that stops loading in some unfinished state on mobile. I'd suggest removing this again.

Yeah, the UI definitely needs some improvement, and could present the situation better.

I appreciate the feedback, and I'll keep that in mind for future design iterations. For the time being, though, I'm planning on keeping this behavior.

Is there a way I can see this on desktop? I tried using dev tools in phone mode but I get the full log still.

I was going to suggest showing the button at the bottom of the loaded text where they'll be looking when it stops loading, similar to where a "next" or "load all" button may be.

Agree on this being pri-3 though.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Viewer should work as well as if you were loading a page of text now (which isn't particularly great on mobile anyways, but we're talking about logs here, so that can't be helped)