HeadingsMap のレビュー
HeadingsMap 作成者: Rumoroso
hmijail によるレビュー
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!
Hoping that the add-on hasn't been hijacked and turned nefarious.
EDITED: The developer answered satisfactorily. Thank you for your work!
開発者の返信
投稿日時: 7年前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
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
合計レビュー数: 58
- 5 段階中 5 の評価Seän "frostbyte" Shepherd によるレビュー (3ヶ月前)
- 5 段階中 4 の評価Joël Bissonnette によるレビュー (8ヶ月前)I like very much this extension. The only annoyance is the font size is too big. Is there a way to change it (and only for HeadingsMap, I don't want to resize the font at the whole Firefox level)?
- 5 段階中 5 の評価Erica Heath によるレビュー (9ヶ月前)Extremely helpful for distilling the structure of html pages. Thank you!
開発者の返信
投稿日時: 1年前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開発者の返信
投稿日時: 2年前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.- I was expecting less and got more. Thank you very much "Rumoroso". It shows entire tree of headings and is very easy to read. When building a website and checking whether all headings are correctly set, it is easy to check it thanks "red outline" effect when heading is accessed. Thank you again for your effort and I wish you good life.
開発者の返信
投稿日時: 2年前Thank you very much for your comment. I really appreciate it and I'm glad to hear that the extension is useful. :) - 5 段階中 5 の評価Firefox ユーザー 16796638 によるレビュー (3年前)
開発者の返信
投稿日時: 3年前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- 5 段階中 5 の評価Ahmed Saeed によるレビュー (3年前)
- 5 段階中 5 の評価Firefox ユーザー 16969514 によるレビュー (3年前)
- 5 段階中 5 の評価Ben Scheffer によるレビュー (4年前)It's great to have an outline for any web page. Especially when the sub-headings in a page all look alike. I don't mind that the outline is part of the document window instead of the browser sidebar. I don't need it for every page and it's just one click away. Only thing that would make it even more handy is a shortcut key.
開発者の返信
投稿日時: 4年前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 ;) 開発者の返信
投稿日時: 4年前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.- 5 段階中 5 の評価Firefox ユーザー 13461889 によるレビュー (4年前)
開発者の返信
投稿日時: 4年前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- 5 段階中 5 の評価FoxWinter2018 によるレビュー (4年前)