Oh!!! :O thank you for letting me know. I was not aware of that bug. I checked and it seems that not always happens, but definitively it happens sometimes. I'll research a bit what could be origin of the problem and fix it as soon I identify it. Sorry for the inconveniences.

Update (18/04/2025): I think I found the issue and fixed it. It should be working as expected as soon it is updated. Thank you again for letting me know about the issue.

Hi, thank you very much for your comment. I will take a look at the problem that you mention. I will prevent the propagation of the keys when the focus is in the search field. Maybe that way the problem stops happening. If that does not work, I can try other alternatives. Thank you again for giving the feedback and also for reporting the issue.
Jorge

Hi, thank you very much for your comment.

The problem with the font being very small is that some time ago I thought it could be good to set the font size style using "rem" units (thinking of the user default font-size), but I didn't expect that a really big amount of websites (and web applications) set the default font-size of the root element to a very low value. :( Those sites then use bigger values in their font-sizes, so they compensate it. I am working in some small fixes that I'll release soon, and it is probable that one of them will be related with this.

Thank you again for your feedback and also for mentioning this problem.

Thank you very much for your comment. I really appreciate it and I'm glad to hear that the extension is useful. :)

I will work on it soon. The problem is that it tries to adjust the original styles that the page has to fit, but there can be many combinations of styles and it is difficult to identify them all or to have something general that works for all pages. If possible, could you please give me an example of page in which the problem happens?
Anyway, I will try to improve how it works.
Thank you very much for your feedback. It's very useful

Thank you very much for the comment. :)

Hi, thank you very much for your comments. Regarding the shortcut key, it is something that I have in my to-do list, and I don't have a good excuse to not having it implemented yet. So this comment works also as push to myself to do it ;)

Hi, I don't have a good answer to that... well, neither a bad one. I have considered it and maybe in the future I'll do it. Hope it is not an inconvenience.

Hi Nando, glad that you find it helpful. And I fully agree with your opinion about having it as part of a sidebar. The first version (many years ago) was made that way and I had to change it because changes in the way in which the browser works. As advantage is that now it is compatible with other browsers, but the drawback is that it does not stay open when browsing. I am really considering alternatives to make it work integrated in a sidebar or even as dev-tools.

Thanks again for your comment

Hi,
Thank you for your comment and suggestion. I never thought of that option but I think it could make sense. I don't know if it is feasible, but for sure I will add it to my to-do list for this extension: https://rumoroso.bitbucket.io/headingsmap/todo.html

Thank you again for writing a comment and suggestion ;)

Hi Doug, thanks for sharing your feedback. I am always happy to know that the extension is useful and also to have this kind of feedback that gives additional ideas of features that it could include.

Regarding your suggestion, right now there is a visual clue that can help to identify the header. Maybe it is not the best way, but I think it could help. If you go to the settings dialog, you'll find one option with the label "Relate with viewport". When it is active, besides each item in the list of headers, at the right, you'll see a grey line that, when you scroll in the page, visually identify the headers (or sections) that are in the viewport area. When writing this comment I am thinking that maybe it is not the best name for the option. I also think that it can be far from your suggestion, but maybe it can help a bit.

Anyway, I just included your suggestion in the to-do list that I have: https://rumoroso.bitbucket.io/headingsmap/todo.html I have to say that some of them have been in the list for some months, so I cannot ensure when are going to be implemented, but at least it is a place to not forget them.

Again, thanks for your comment and your feedback