71–80 of 246 posts
Can you please avoid blurring the prior column (or at least the comment you came from)? It's useful to see context that way. Otherwise I think it's really good. Reddit should have aspired to something this well thought out. (I'd also like page up / page down.)
Front end bug on mobile. As you down arrow the faded part at the top gets smaller and smaller. Chrome on Pixel
I'd just ask for a dark theme based on the browser's preferences.
Definitely gonna add an optional dark mode soon!
+1 for dark mode. But also, would you add a shortcut for the left hand for opening comments? I lost my right arm in a tractor accident, and pressing O is a bit annoying.
Just kidding, but I do like the idea of R to reply.
Earlier quoted context omitted.
How do I read the comments?
You have to use your arrow keys, WASD or HJKL to navigate through the comments.
I was trying to create some web-UI like this to read my own dump of bookmarks/notes on various devices.
What language/frameworks did you use for the web UI?
Is the source available somewhere gitlab/github?
P.S. As a default workaround for HN design issues I use lynx with vim bindings. This gives me font clarity and minimalistic interface.
Earlier quoted context omitted.
Yes, but "enabling keyboard navigation" shouldn't mean disabling mouse based navigation. There are multiple people on this thread who are confused because of disabled scrolling which shows that it's bad UX. > If you don't like it, just use Hacker News. Yes, I will not be using this site. Just giving my feedback and opinion on the UX just like you.
> Yes, but "enabling keyboard navigation" shouldn't mean disabling mouse based navigation If someone shows me a project for keyboard navigation, I won't complain that there is no mouse navigation, as that would go against the very nature of the project. > Yes, I will not be using this site. Just giving my feedback and opinion on the UX just like you. But you're not actually giving any useful feedback on the UX the pe…
It seems to me removing scrolling is actually work as opposed to just letting the default behavior of the browser to prevail. I'm not saying there is no point in having a site with keyboard navigation as the primary mode of interaction. It's just that when you go out of your way to remove something that should be supported natively you're scope creeping.
If losing selection highlight is a problem just disable that feature only why mess with scrolling?