unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Nic Ferrier <nferrier@ferrier.me.uk>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: "modern" doc viewer for info/html
Date: Sat, 2 Aug 2014 12:47:41 +0700	[thread overview]
Message-ID: <CAP_d_8Vy_OvAO8gyxwwKDkoZ7+a2Zo4nqGxk1Pj6NOfUdafC6g@mail.gmail.com> (raw)
In-Reply-To: <87wqarkbrw.fsf@ferrier.me.uk>

On Sat, Aug 2, 2014 at 6:53 AM, Nic Ferrier <nferrier@ferrier.me.uk> wrote:

> Here: http://gnudoc.ferrier.me.uk/
>
> is something that (I think) Bob Chassell challenged me to do 10 years
> ago. A "modern" HTML based viewer for info/html.


Ten years ago it might not be evident (Firefox was called Firebird
back then), but nowadays, when you use a printable character as a
navigation command in a Javascript application, you need to invoke
preventDefault() on the event object. Otherwise, in certain browser
configurations, the character may start an incremental search.

Case in point: I am using Firefox 31, with Preferences | Advanced |
General | [x] Search for text when I start typing. I click any link on
the front page, which displays that node. I then press 'l' on my
keyboard. This takes me back to the index and starts an incremental
search for 'l', which it finds in the 'Lisp Data Types' link. The
incremental search bar grabs keyboard focus, remains active for a few
seconds, and then disappears without returning focus to the page. As a
result, I cannot use any further letter-based navigation commands.


Unrelated: Some links in the top-level index occupy two lines, but
nothing in their appearance gives a hint about that. The list reads as
if it were:

* …
* Packaging
* Antinews
* GNU Free
* Documentation License
* GPL
* …



  reply	other threads:[~2014-08-02  5:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 23:53 "modern" doc viewer for info/html Nic Ferrier
2014-08-02  5:47 ` Yuri Khan [this message]
2014-08-02  8:55   ` Nic Ferrier
2014-08-02  6:46 ` Eli Zaretskii
2014-08-02  8:24   ` Nic Ferrier
2014-08-02  9:20     ` Eli Zaretskii
2014-08-02  9:34       ` Rasmus
2014-08-02 10:30         ` Eli Zaretskii
2014-08-02 11:12           ` Nic Ferrier
2014-08-02 11:18             ` Lennart Borgman
2014-08-02 12:26               ` Nic Ferrier
2014-08-02 12:30                 ` Lennart Borgman
2014-08-02 12:24             ` Eli Zaretskii
2014-08-02 14:05               ` Nic Ferrier
2014-08-02 11:13         ` Nic Ferrier
2014-08-02 15:51         ` Richard Stallman
2014-08-02 15:50     ` Richard Stallman
2014-08-02 16:18       ` Nic Ferrier
2014-08-02 22:17         ` Rasmus
2014-08-02 23:32           ` Nic Ferrier
2014-08-03  0:45             ` Lennart Borgman
2014-08-03  4:50             ` Richard Stallman
2014-08-03  4:49         ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP_d_8Vy_OvAO8gyxwwKDkoZ7+a2Zo4nqGxk1Pj6NOfUdafC6g@mail.gmail.com \
    --to=yuri.v.khan@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=nferrier@ferrier.me.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).