The node I replied to was about HTML accesskeys. What you are doing seems quite unrelated to that. Note that I said:
" Perhaps you are thinking of scrolling within a thread, but I don't think access keys can be used that way (without doing a lot of JavaScript...). "
You seem to be doing a lot of javascript, no? And you don't seem to be using HTML accesskeys at all.
but a previous keystroke has to establish the context for it, and that keystroke should scroll the context into view
And does scrolling the content change the context? Is there a visual indicator of what the current context is? You might want to consider those points if you haven't. These are some of the issues that crossed my mind such that I decided to not further discuss the idea beyond my brief mention.
I'm glad you appear to have made something that is useful to blazar. Personally, I scroll a thread when I'm done reading/scanning what currently is displayed not in increments of nodes. But I appreciate the potential improvement for others.
- tye
In reply to Re^5: Better keyboard-driven navigation, any? (possible)
by tye
in thread Better keyboard-driven navigation, any?
by blazar
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |