The comments don't render correctly on FF on Android. They all render one after another and it's impossible to tell which comments are replies and which aren't. :(
Can you also switch from the current indentation layout (via images in a table) to a div-based layout where all subcomments are inside the element of the parent comment?
I actually find myself reading the site considerably less because of this, I'm sure I'm not the only one. Please let me set a cookie to keep the desktop version!!
A way to collapse replies would also be appreciated. Sometimes I just want to read the top-level comments and scrolling through dozens of replies to find the next topic of discussion can be frustrating.
I'd like to second this one. Sometimes the top comment ends up being one of those that spawns a gigantic and completely unproductive conversation, and it would be nice to be able to move past it easily.
That way you'd have to scroll down+right to follow a thread, but at least you could tell the difference between children and siblings, and never get super-narrow posts deep in a thread.
Some deeply nested conversations get the formatting hammer after a certain depth. A gentle slide to the right suddenly becomes 2" or more, with text jammed into half an inch of screen width.
Yep - it would also be great if HN provided an indicator of which way you voted. As it stands, I'd say I probably get it right about 75% of the time, but who knows? It's impossible to tell if you've upvoted or downvoted a comment still; and especially on mobile, I bet I get it wrong pretty often.
You're on iPhone aren't you. Having used both iPhone and Android for some time now I think its crazy how much more accurate Android is with pointing at small links on-screen. And in the rare instance it's not confident about what you meant to push, it will zoom in a bubble and ask you to click again (confirm), where the iPhone will just not do anything.
Can the upvote and downvote triangular arrows be given more separation? On my Firefox Mobile, they appear together vertically close together and I fear I may tap on the wrong one.
Whooooooo! Thank you dang and team. I have been very critical of the site's mobile unfriendliness in the past. Now I can use this as an example of a small change that makes a big difference. Certainly better late than never. You have probably saved me thousands over the lifetime in new glasses and contacts.
On Windows Phone (I know, fringe audience, but I love it), I need to slightly adjust the zoom level on the comments view pages. The viewport is slightly narrower than the page's content, by about 15%.
But otherwise, and even with that small matter, it's a change that makes mobile use easier. Reading has always been fairly easy on mobile in my opinion, but clicking the right thing (e.g., the comments links) required either zooming or very careful aim. It's nice to not have that challenge any more.
I will echo the request for a bit more indentation for child comments. But I also understand the hesitation to add too much indentation given the narrow viewport.
Doesn't work on my tablet, I get the desktop website with tiny letters. If I zoom in, I have to scroll horizontally to read the comments, which is a pain in the butt.
I'm surprised this wasn't announced officially by dang. I spent some time the other day searching for the official announcement of HN's new responsive design, and just figured I must've missed it.
Seems like the last week or so the comment indentation has been worse on Android with Chrome on a 7" tablet. It used to be a larger indent. Now I can't tell who's replying to what without thinking about it.
They've been telling client developers that they should move from screen-scraping to using the API (https://github.com/HackerNews/API) for a while now. I don't know if that's the problem with this specific client, but you may want to check with the developers and see if it is, and if so, what their ETA is for getting onto the API.
The issue with the current API is that it's read-only, so clients can't completely migrate to it. Using a combination of the API for reads and scraping for checking responses to writes makes things a bit difficult.