Mathieu Lirzin <m...@gnu.org> writes: > Hello, > > Mathieu Lirzin <m...@gnu.org> writes: >> >> Assaf Gordon <assafgor...@gmail.com> writes: >> >>> 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). >> >> Noted, I have been able to reproduce this with Chromium 59. With >> Firefox 54 the focus works fine. > > I have partially fix this in commit > 895c5da903cd991aa6678dc075e534d5663aaa73 > > The remaining weird issue is that with Chromium 59, focus is working > when using the "file:" protocol but not when using 'http(s):': > > https://www.gnu.org/software/texinfo/gsoc-2017-js-example/kawa
After doing some tests with a local basic http server, the problem seems specific to 'gnu.org' with Chromium. -- Mathieu Lirzin GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
