Re^5: Better keyboard-driven navigation, any? (possible)

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

Comment on Re^5: Better keyboard-driven navigation, any? (possible)

Replies are listed 'Best First'.
Re^6: Better keyboard-driven navigation, any? (possible) by shmem (Chancellor) on Jul 25, 2008 at 09:50 UTC
The node I replied to was about HTML accesskeys. What you are doing seems quite unrelated to that. The node you replied to was about FF3 and HTML accesskeys, but you wrote about navigation, which the node you replied to did not even mention. You were replying to that node and the OP, which is what I did, too. And to the entire thread. The part of your reply I referenced was not about HTML accesskeys. I didn't use HTML accesskeys in the first place because I didn't know about them. After reading a bit, I think they provide no advantage over a plain JS solution since they are not context-aware. Perhaps Opera provides for that, I don't know. And they rely on modifiers, which isn't necessary. Scrolling the context changes the context cursor which is currently not visible, so yes, highlighting is necessary. --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply] [d/l]

Replies are listed 'Best First'.

Re^6: Better keyboard-driven navigation, any? (possible)
by shmem (Chancellor) on Jul 25, 2008 at 09:50 UTC

The node I replied to was about HTML accesskeys. What you are doing seems quite unrelated to that.

The node you replied to was about FF3 and HTML accesskeys, but you wrote about navigation, which the node you replied to did not even mention. You were replying to that node and the OP, which is what I did, too. And to the entire thread. The part of your reply I referenced was not about HTML accesskeys.

I didn't use HTML accesskeys in the first place because I didn't know about them. After reading a bit, I think they provide no advantage over a plain JS solution since they are not context-aware. Perhaps Opera provides for that, I don't know. And they rely on modifiers, which isn't necessary.

Scrolling the context changes the context cursor which is currently not visible, so yes, highlighting is necessary.

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

[reply]
[d/l]