- 5 段階中 5 の評価Firefox ユーザー 16124644 によるレビュー (3年前)Very nice extension, does exactly what I expected.
There is only one feature I miss. If I am at a certain tag in the HTML document then I would like to show it in the add-on's panel.
Now only the opposite direction works: I can click on the add-on's panel so that the HTML document scrolls to the given heading. What I would like is to right click on a heading within the HTML document and want the add-on panel to be scrolled there.
開発者の返信投稿日時: 3年前Thank you very much for your comment, and specially for sharing the idea of that potential new feature (which by the way I like). I will include it in the "to-do" list. I think this can go in parallel with other that is also in the list, which is to somehow show reflect the position of the scroll in the page regarding the headers, with the headers in the extension.
- 5 段階中 4 の評価grahamperrin によるレビュー (3年前)https://addons.mozilla.org/en-GB/firefox/addon/headingsmap/versions/3.7.0/updateinfo/ empty; release notes please.
Edit: thanks for adding the notes!
開発者の返信投稿日時: 3年前Ups, true. I just updated its content. I already did it when uploaded this version, but my fault, it seems that the change was not submitted. Thanks for letting me know
- 5 段階中 3 の評価Firefox ユーザー 15126594 によるレビュー (4年前)Really useful extension! However, I didn't find a way to map shortcuts, therefore I have to look for another solution :( Thanks anyway.
- 5 段階中 3 の評価Kiiviak によるレビュー (4年前)The extension greatly improves navigation. It is marked as available under the Mozilla Public Licence in the "More information" panel of the Firefox add-ons catalogue but I was not able to find its source code so far. Would anyone know about the repository location? Unless there's an error with the licence?
- 5 段階中 5 の評価Firefox ユーザー 14460640 によるレビュー (4年前)Great extension! It gives an instant Table of Content on a webpage that properly use heading elements!
One improvement that is really glaring:
* Add to Firefox Sidebar so it won't block the page itself
開発者の返信投稿日時: 4年前Hi, thanks for your comment and rating.
Regarding to the sidebar, I totally agree with that idea. The extension, while XUL could be used for integrating it in the browser, was always a sidebar panel, so it was perfect because it didn´t interfere in the page and, additionally, could be open while browsing between pages.
That had to change with the new webextensions API. The advantage of this change is that the same development works for other browsers.
I have in mind to try to include it again as sidebar panel. Right now I am working in a change for giving additional feedback for SEO analysis. Once it is done, I will try with the panel ;)
Again, thanks for your comment. This kind of feedback keeps my motivation for trying to make it better ;)
- 5 段階中 5 の評価hmijail によるレビュー (5年前)Seems to work OK, but lately there's updates in rapid fire (multiple per day??) and the size has doubled with no release notes provided, which makes me suspicious. What is going on?
Hoping that the add-on hasn't been hijacked and turned nefarious.
EDITED: The developer answered satisfactorily. Thank you for your work!Hi hmijail, thanks for your comment and feedback. I think it is very useful and made me see other point of view.
The weight that the extension has now is caused by an error that I made when including the spinner-gif that is shown when generating the trees (the HTML5 outline takes time and I thought it was good idea). I just realised of it because you mentioned it. The problem is that I didn't optimise it (maybe half of the size is because that gif). I will fix it in the next release.
Regarding to the often updates, to be honest, I didn't think that could generate some concerns, but it is good that you brought that idea to me. I have been adding lots of changes that mean some new features, also improvements in the performance and a couple of bugfixes. I usually release the changes as soon as I apply them, instead of waiting for having a bunch of them done. I would say that it is more like a continuos delivery than a scheduled releases. I think that, after this, creating a page with the release notes could be a good idea, so they can be accessible for anyone. Just to cover a bit my lack on creating those release notes, some of the changes I introduced this week are:
* New features (some of them):
- new panel for settings (it appears inside the panel)
- new dark theme
- option for including the aria-label content
- resizer for the panel
- option for placing the panel in the right side
- CSS overscroll-behavior property set to none for preventing the scroll of the page when the tree has scroll
- refactor in the code for improving the speed in which the trees are generated
- only the tree of the current tab is generated (before this, both trees were generated always)
- better DOM structure of the content
I also applied some minor changes that made the code more clean and structured and also some bugfixes. Ah, and I updated the code so the version for Chrome of the add-on shares the same code, helping me in the development process because there is no duplicated work.
So just for finishing this long comment, I can tell you that the add-on hasn't been hijacked and still keeps the initial intention that always had. Anyway, I guess that if that would be the case, the Mozilla review (step that is executed before any release) would block the release of the add-on.
- 5 段階中 3 の評価Emmanuel によるレビュー (5年前)Nice and usefull addon!
Would be nice if one could open/collapse all the titles together, and eventually memorise this when reloading the page.Hi Emmanuel, thanks for commenting and also for giving suggestions. I will consider the open/collapse all and if it could be something that could be persisted. I have some doubts about how useful could be this second option (persisting the state), but maybe I can find a middle point (something like offering a configuration option for showing the results initially collapse at some defined level in the hierarchy).
Again, thank you very much for the feedback.
- 5 段階中 5 の評価tkupna によるレビュー (5年前)förenklar avsevärt vid sökning av något specifikt vid besök på större websajter ex kommuner och övriga myndiheter
- 5 段階中 5 の評価Firefox ユーザー 14038117 によるレビュー (5年前)Thanks for making this! One thing I would like would be a way to specify the color scheme of the outline page. Even a simple checkbox to enable a dark mode with inverted colors, would be fantastic as an initial easy option.
UPDATE: The additional dark theme option is great! Thanks for the update!Hi, thanks for your comment (I know, I waited too much for answering :( ). I just added some changes and one of those is the "dark" theme as option (selecting it is possible in the configuration page of the extension). I hope it helps.
- 5 段階中 4 の評価Sebastien Billard によるレビュー (5年前)Happy to see the extension is back ! One regrets and one suggestion though :
- If I remember well it used to highlight the headlines clicked in the left panel ?
* Yes, the header was highlighted when clicking on the correspondent one in the panel (I have to recover the feature -most probable as option-... since the whole extension was refactored almost from scratch, there are features that are still pendant of being added/recovered). So thank you for commenting it because helps me in the prioritization of tasks
Again, thank you very much for your feedback and comments.
- 5 段階中 5 の評価Firefox ユーザー 12808576 によるレビュー (5年前)Provides an outline for a HTML page. Exactly what I need.
- 5 段階中 5 の評価Brett Zamir によるレビュー (5年前)Very useful, and glad to have back again!Hi, thanks for the comment. I still want to do some improvements like evaluating inside frames or try to integrate it as a panel in the browser.
Thanks again for the comment and any feedback is always very welcome.
- 5 段階中 5 の評価Kermit-The-Frog によるレビュー (5年前)Finally back on Firefox and the level numbers are back again. :)
You could even make it lighter and get rid of the HTML5 Outline tab as it's definitely not relevant any more, but hey...
Great work anyway and thanks for this neat little tool.Hi, thanks for your comment. I was considering removing the HTML5 Outline as well. It is probably that I will do it since it is not worth to use resources that could affect to the performance on something that is not relevant any more.
Again, thanks for your feedback ;)