HeadingsMap

Hello Joël, I've made the extension using standards, and that is what makes the same code (and the extension itself) compatible and available in other browsers (like Firefox). The reason is to simplify and increase compatibility (basically, one of the principles of the standards). I didn't pay attention to other browsers like Vivaldi or Brave, and I won't do it (for now, and while I do not have more time). Although those browsers announce they can use the extensions available in the Chrome store, if the extension works in Chrome and does not work on one of them, I would consider the issue is on their side, and in their announcement, so I would reach out to them and question it.

Hi Алексей, thank you for your comment. It was removed because there are no tools, user agents, assistive technology, or any other software taking advantage of it. The algorithm was developed many years ago, when the Web was evolving to a context with more reusable content, and it was meant to generate blocks of content with their hierarchy and structure. You can read about it (check the years): * https://www.accessibility-developer-guide.com/examples/headings/html-5-outline/ * https://www.smashingmagazine.com/2011/08/html5-and-the-document-outlining-algorithm/ The extension used that algorithm to analyse the documents, helping with proper implementations. Since there was no interest in implementing the algorithm, the extension was in reality checking things against something that was neither correct nor wrong, just deprecated. Anyway, after some users contacting me to ask about it, I decided to bring it back. It is already available in other browsers, and it will be available soon on Chrome (it takes some time between uploading it to the store and its validation). Since it seems that it is being used for a purpose that was not meant for, I am not fully aware of how users are using it. If someone thinks the "HTML5 Outline algorithm" is like a valid outline for the documents, he/she might be considering things that are not the best. The outline of the document, the one used for semantics and structure, as well as for assistive technology, is mainly based on heading structure and ARIA landmarks. Those are the relevant elements to pay attention to when considering accessibility and user benefit. edit 4/14/2025: since I cannot add another comment, I edit this one. Today it was released the version that brings back the functionality.

Hi Johnny, I am not sure what you mean about the organization for links in that page and so on. Are you sure you are talking about the extension? Are you using this space just to share that link? To be honest I don't know what you are talking about. Could you please be a bit more specific?

Hi Zytronium, thank you for sharing your feedback. I always appreciate having feedback, so I can improve the extension based on that. In my opinion, it is not fair to base the rating of one extension meant for Chrome on how it works in a different browser that is not meant to work on. Anyway, I can understand that maybe your comment could be useful for other users of the browser Brave. I assume that the developers of the browser Brave are the ones that ensure that it is compatible with the Chrome extensions, but not the other way around, so I wouldn't expect a Chrome extension developer to ensure the extension is compatible with other browser. This extension is placed in the Chrome browser store because is meant to work in Chrome. The same extension code works for three major browsers without the need of adapting anything, and I do not build the extension to work in other browsers. I understand your point, and I hope you understand mine. Maybe at some point I would check if I can make it compatible with more browsers, but there are features that are waiting that most likely would have higher priority. Thank you for editing you comment to add the last paragraph. I think it would be great if the whole comment starts with that paragraph, so any person that starts reading it, understand the context, but I guess the platform does not allow that.

Hi Mizanulhaq, first of all, thank you very much for sharing your opinion. Regarding the number that appears beside each heading in the tree, to hide it you can do the following: * go to "settings" (the three dots button in the top opens a menu, and the first option is "settings" * this opens a dialog with three tabs. The second one is "headers structure tree". Go to that tab and uncheck the option "show heading level". I hope this is what you needed. And thank you again.

Hi D Brown, thank you very much for sharing your comment. I really appreciate it.