[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: info.js bugs

From: Per Bothner
Subject: Re: info.js bugs
Date: Fri, 24 Dec 2021 22:47:15 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0

I checked in fixes for these problems. I also uploaded an updated 

On 12/21/21 12:28, Gavin Smith wrote:
Unrelated to your original message, but looking at those pages, I
noticed a few problems with info.js:

* Typing "i" brings up the index search box, but there is no index
in the document.  Showing a message "No indices" would be better
than a text entry box.

It now shows "No index in this document" by analogy with
'm' showing "No menu in this node".

* The browser tab is named starting "Top (DomTerm..." regardless
of which page is being shown.

Checked in code to update the window/tab title.

* When pressing "s" for search, it's very easy for the search box
to contain the letter "s", even if the default is something else.
To trigger: hold down the "s" key, then press Escape.  Then press
"s" again.  There is an "s" stuck in the search box.  (I couldn't
break this reliably.)

There was a related problem: Typing 'm' or 'i' would often initialize the
minibuffer with those letters.  The problem was likely that key
events would get passed to the minibuffer element after it got focus.
Seems to be fixed by adding a call to preventDefault on the keydown event.
        --Per Bothner
per@bothner.com   http://per.bothner.com/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]