> 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 person has implemented, you're giving feedback towards some UX that doesn't exist and won't exist as it's outside the scope of the project.
It's like someone showing you that they built a car for themselves, and your first comment is "but does it float in the sea?". No, of course it doesn't float, it's not a boat.
I think you’re being a little defensive. People might like the graphical design but not the control scheme. In that case I think it’s fair to say that. Sure it might intended as a keyboard site but that doesn’t mean the author couldn’t enhance in that, even pivot, if he wanted to.
To use your boat example: there is no point trying to sell kit cars if people are only interested in buying boats.
Ok, this is a pet project so the author might have no intention of taking his design and trying to monetise it. But as long as feedback is civil I can’t see why opposing opinions can’t be shared (and ignored if the author so chooses).
I know on my personal projects, comments that seem to miss the point often then inspire me to create new things. So I’m always interest in any feedback. Just as long as it’s not people moaning about the name lol
> some UX that doesn't exist and won't exist as it's outside the scope of the project
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?
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 person has implemented, you're giving feedback towards some UX that doesn't exist and won't exist as it's outside the scope of the project.
It's like someone showing you that they built a car for themselves, and your first comment is "but does it float in the sea?". No, of course it doesn't float, it's not a boat.
How is that useful feedback to this project?