Everything is inacessible in text-only browsers

[Gankra]

Tested in elinks from brew:

basically works with noscript

• https://www.rust-lang.org/ - SSL error
• https://doc.rust-lang.org/ - Bad HTTP response
• https://internals.rust-lang.org/ - After a couple minutes of downloading a few kb/s - error reading from socket
• https://users.rust-lang.org/ - ditto

Doesn't even work with noscript (but does, you know, render something)

• https://crates.io - What would you like to do with the file (type: application/json)?

[alexcrichton]

Is... this a bug? Sounds like this is working as intended...

[Gankra]

@alexcrichton I can't tell if you're joking or not

[alexcrichton]

I'm semi-joking, but I personally don't see the benefit in investing time to get text-only browsers working.

[alexcrichton]

Ah @gankro cleared up my confusion that this is not solely meant for those who prefer to surf the web from a terminal, but rather this enables many accessibility programs to "Just Work" on many sites, which I'm more than ok with!

[Gankra]

CC rust-lang/crates.io#173

[nodakai]

www.rust-lang.org, doc.rust-lang.org and Discourses are usable with w3m at the moment.

crates.io is not:

This site requires that JavaScript to be enabled.

I thought all of its contents were nothing more than static HTML/CSS... (I should have probably posted to rust-lang/crates.io )

[steveklabnik]

Crates.io has its own issue open. I recently upgraded Ember, which will give us FastBoot when it's ready.

[nox]

How far is FastBoot?