1269634 - Unexpected experience when site serves JSON error page

Status: NEW

(DevTools :: JSON Viewer, defect, P3)

Description

[Justin Dolske [:Dolske]]

Attachment: Screenshot, old experience vs new

I was surprised to suddenly get dropped into the JSON viewer... I had just done a search on imgur.com, then did another search, and found myself in the JSON viewer. Turns out I happened to do this just as the site became overloaded, and somewhat oddly it's returning an HTTP 500 with JSON.

Not sure if this is desirable or not. This may very well end up as wonfix/invalid, but filing anyway. :-)

On the one hand, if a random site sends back JSON, the user -- who is presumably not a web developer -- has already lost. If the site's not sending content that a browser can meaningfully render for a normal end-user, well, there's just not much we can do.

On the other hand... At least in this particular case, the JSON is mostly-readable. And a stark black-and-white page with computery-stuff does convey "something is broken" much more than the sleek and refined JSON viewer UI.

Is this intended? Should we perhaps show some kind of interstitial page if the user has never opened the devtools before? Or show the raw JSON + an info bar to enable the JSON view (perhaps by default)?

Getting dropped into the JSON viewer unexpectedly is kind of disorienting, but it's unclear if the alternatives are all that much better.

Comment 1

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Helen do you have any opinions on this from the UI/UX perspective?

Not sure if there is anything we can do with this, but note that JSON Viewer is currently *not* enabled in the Release channel when majority of users is so, *non-developer* user should be fine I guess.

Honza

Comment 2

[Zac Svoboda :zacnomore]

Looks like Helen's account is disabled now, who else could provide a decision?

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:Honza, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?

For more information, please visit auto_nag documentation.

Comment 4

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Note: JSON Viewer is now enabled on all channels.

I tend to think that we should close this as wontfix.

But, one thing we could do is disabling the JSON Viewer if the user never opened DevTools and provide simple UI to enable it (by opening DevTools?).

This migt be related to the same thinking behind "Accidental usage of F12"
Julian, what do you think?

Comment 5

[Julian Descottes [:jdescottes]]

It sounds fine to disable this if devtools are disabled explicitly. Blocking 1704519.