Re: [GSoC] Javascript for info-style navigation

[Gavin Smith]

On Wed, Jun 28, 2017 at 03:40:09PM +0000, Assaf Gordon wrote:
> 3.
> Keyboard scrolling of the content pages isn't always working.
> Example (in Chrome 59):
> 3.1. Load this page:
>     http://www.gnu.org/software/texinfo/gsoc-2017-js-example/kawa/
> 3.2. Press "N" once (you should be at "News - Recent Changes" which is a long 
> page.)
>     now pressing "space" or "down arrow" does not scroll the page
>     (which kinds of defeat the entire keyboard navigation...)
> 3.3. If you click once (with the mouse) inside the content pane,
>     it does get the focus and from now on space/down arrow will work
>     in this node only.
> 3.4. Press ']' to move to the next node - keyboard navigation
>     doesn't work.
> 3.5. Press '[' to move back to the "News - Recent Changes" node) -
>     keyboard navigation works again
>     (If I had to guess - that node's element kept the focus).
> 

FWIW this works for me in Firefox 53.

> 4.
> There's some inconsistency in the menu navigation of the left-side bar.
> Example (in Chrome 59):
> 4.1. Load this page:
>     http://www.gnu.org/software/texinfo/gsoc-2017-js-example/kawa/
> 4.2. Press "N" three times (should be on "The Kawa Community" node)
> 4.3. Press "]" once (should be on "Reporting bugs" node)
> 4.4. Press "N" five times (should be on "Ideas and tasks for contributing to 
> Kawa" node)
> 4.5. Press "]" once (should be on "Run interactive process in separate JVM")
> 4.6. Based on the menu structure, I'd expect "N" to work and move
>     to the next item on the same level (at least as displayed
>     in the left-side menu). But it doesn't.
>     "P" and "U" also don't work.
>     Only "[" and "]" do.

I think that either the subsections in a single page should be ignored
by the keyboard navigation commands, or treated equally to subsections 
in separate nodes.  At the moment it is a mixture where they are treated 
as separate nodes for "[" and "]" but not for "n" and "p".