Viewing HTML body content is painful about htty HOT 7 CLOSED

Should the browser then replay the whole request history? That could be slow and convoluted.
Or do you just want to see a rendering of the *HTML in response body, as it is?

from htty.

The latter. I’m thinking maybe we write the body of the response (or the request) to a temp file and then launch the default browser to view it.

from htty.

Sounds somewhat useful, but that's not going to allow JS running in that page to access cookie/session storage, or resources that are linked relative to the original domain.

from htty.

Agreed. I was thinking of this as a WYSIWYG preview rather than “let me start using the browser where htty left off.”

Perhaps that makes it more annoying than useful.

Would it be better to attempt a Lynx-style text-only rendering of the markup?

from htty.

If you do that (and a couple more things, like curses, and general usability) – and that's not a small task, but if you would set out to – you would be getting SEO/crawler/accessibility so much easier. This could later be extended to request sequences that can be replayed by HTTY, by the text-only browser, and by the default graphical browser. And those sequences could become trees, with multiple routes you could take, etc.
And then you'd solve the World in 42 steps.

The WYSIWYG preview is really just fine. It's a visualisation of the response body, nothing more; it is useful on it's own. Not plenty useful, but nice to have.
You should choose your battles.

from htty.

See http://github.com/htty/htty/issues/#issue/17.

from htty.

v1.3.0 (just released) includes new commands body-request-open and body-response-open for launching the default viewer assigned to the content type. Options allow you to override the default viewer launched (e.g., use Firefox instead of Chrome).

from htty.