- scottobob によるレビュー (5ヶ月前)5 段階中 4 の評価If the page being annotated is already a local file, then SingleFile should save back to that file instead of making a new file in the Downloads folder.
This would be useful when re-annotating a file you've already saved.
Edit 1: There is an option "File name > filename conflict resolution" but this provides no way to save to the original file except by renavigating the whole path to the original html source file, and re-specifying the filename.
What I'm asking for is that SingleFile literally saves back to the original source html file (possibly with an overwrite warning for safety, although I would be happier without that).
Edit 2: disabling the option "File name > open the "Save as" dialog to confirm the file name" doesn't affect this problem; the file is still written to the Downloads directory instead of its original location.
開発者の返信投稿日時: 5ヶ月前There is an option for that, see "File name > filename conflict resolution".
Edit 1: I think it's possible by also disabling the option "File name > open the "Save as" dialog to confirm the file name" (this is the default state)
Edit 2: It's technically impossible for an extension to save the file in another folder than the "Downloads" folder or its subfolders.
- Firefox ユーザー 15035683 によるレビュー (1年前)5 段階中 4 の評価Works well, I wish there was an additional setting where you could choose where the file goes automatically, without changing the download location in Firefox, as I prefer all my saved pages in a different location than all my other downloads go to. (I currently have to move all the saved pages from "~/Downloads" to another folder.)
- browser.tech によるレビュー (1年前)5 段階中 4 の評価I tried SingleFile briefly. It works. Looks like a well thought out and put together addon.
One thing I noticed, when you have the option enabled for "include the info bar in the saved page," the page actually shows a floating icon in the upper corner. If you click on this icon a flyout will indicate the time the page was saved, then if you hover over a tiny button on the flyout the original URL will popup. Clicking the tiny button takes you to the original URL.
This all looks nice, but I prefer the way Save Page WE does it. Save Page displays a fixed header bar with the full URL and time the page was saved. For someone like me who's always paying attention to the URL bar this is nicer. It's easier to understand that the page you're viewing is an archive, and easier to get to the original page with a single click.
Note that both the floating icon in SingleFile and the header bar in Save Page WE can be closed.
I also notice that neither SingleFile or Save Page WE works in FireFox reader view. A small thing, but it would be nice. That's what I was really looking for when I tried SingleFile.Thanks for the review. It is technically impossible to make an add-on run in the reader view. However, you can format the page, as the reader view does, in the annotation editor by clicking the button "format the page for better readability" (page with glasses icon) when present.
- piecevcake によるレビュー (1年前)5 段階中 4 の評価Excellent well structured and many options.
A pity the annotated pages are lost between sessions. Otherwise it would replace all the markup addons as well!
Would have 5 stars if it worked on moz pages.
Reply to Dev- THIS page for example, and addons page. Will open on githubThank you for the review. That's unfortunately impossible from a technical point of view to save a moz: page. I do not know what moz: page you want to save but if that's the reader view, note that there is a button in the annotation editor to format the page like in the reader view. If you have an account on github, I recommend to open an issue if you want to discuss about this.
THIS page cannot be saved with Firefox because Mozilla blocks extensions on some of their domains. You can use another browser like Chrome to circumvent this limitation though.
Works great! However, I really feel like saving scripts, audio elements, etc. should be enabled by default.Thank you for the review. The default settings are optimized to produce light (and faithful) snapshot of pages because this was the most recurrent complain in the past. That's why the options you mentioned are disabled. Note also that disabling the option "remove scripts" can, unfortunately, lead to corrupted pages.