Hi Nijaz, thanks for your comment. Knowing that the extension is useful always makes me happy ;)

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.

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

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 ;)

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
- ...
* Performance:
- 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.
Thanks

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.

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.

Hi Sebastien. First of all, thank you for your feedback. Regarding to your comments:

* 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

* I would like to know the use case for retrieving the headers structure for the HTML that is not modified by javascript. The tools is initially meant for giving the structure that the browser renders, so the one that the HTML has without any behavioral change was not considered. In order to consider implementing that feature, I would like to know and understand the use case. Could you please give me some feedback on it?

Again, thank you very much for your feedback and comments.