Save Page WE のレビュー
Save Page WE 作成者: DW-dev
DW-dev による応答
開発者の返信
投稿日時: 8年前In reply to a couple of the points raised:
1) With regards to the saved file format:
The page source (HTML) and all of the referenced resources are saved in a single file (.html).
External CSS style sheets are converted to internal CSS style sheets. All other textual resources (scripts & frames) are stored as UTF-8 data URIs.
If the page loader is not used, all binary resources (images, fonts, audios, videos, etc) are stored as Base64 data URIs. In this case, if a binary resource is referenced multiple times, a Base64 data URL will be stored for each reference.
If the page loader is used, all binary resources (images, fonts, audios, videos, etc) are stored as Base64 strings in the page loader script, and are converted to blob URLs when the save page is opened. In this case, if a binary resource is referenced multiple times, its Base 64 string will be stored only once, resulting in much smaller saved files.
2) "When I reopened that page ... most of the images were lacking and much of the layout was somewhat off."
The reason for this discrepancy is that, when you saved the page with Save Page WE, you had the 'Use page loader to reduce file size' option enabled, which means all of the binary resources are represented as blobs.
Before using the Firefox 'Save Page As', you need to use the 'Remove Page Loader' menu item that is built into Save Page WE. Alternatively, you could disable the 'Use page loader to reduce file size' option before saving the page with Save Page WE. Either way, you should find that the re-saved page is pretty much identical to the original page.
1) With regards to the saved file format:
The page source (HTML) and all of the referenced resources are saved in a single file (.html).
External CSS style sheets are converted to internal CSS style sheets. All other textual resources (scripts & frames) are stored as UTF-8 data URIs.
If the page loader is not used, all binary resources (images, fonts, audios, videos, etc) are stored as Base64 data URIs. In this case, if a binary resource is referenced multiple times, a Base64 data URL will be stored for each reference.
If the page loader is used, all binary resources (images, fonts, audios, videos, etc) are stored as Base64 strings in the page loader script, and are converted to blob URLs when the save page is opened. In this case, if a binary resource is referenced multiple times, its Base 64 string will be stored only once, resulting in much smaller saved files.
2) "When I reopened that page ... most of the images were lacking and much of the layout was somewhat off."
The reason for this discrepancy is that, when you saved the page with Save Page WE, you had the 'Use page loader to reduce file size' option enabled, which means all of the binary resources are represented as blobs.
Before using the Firefox 'Save Page As', you need to use the 'Remove Page Loader' menu item that is built into Save Page WE. Alternatively, you could disable the 'Use page loader to reduce file size' option before saving the page with Save Page WE. Either way, you should find that the re-saved page is pretty much identical to the original page.
合計レビュー数: 447
- 5 段階中 5 の評価Firefox ユーザー 16745788 によるレビュー (20日前)Большое спасибо! Пользуюсь редко, но выручает именно она
- Dear Developer,
I’m writing to provide feedback on Save Page WE. I’ve noticed that the extension saves the web page exactly as it is rendered at the moment of saving. As a result, any content hidden behind spoilers (which remain collapsed) is not included in the saved file. This has been somewhat inconvenient, as I often need to preserve the entire content of a page.
Would it be possible to add an option in the extension’s settings to automatically expand spoiler sections (or other similar hidden elements) before saving the page? This feature would greatly enhance the usefulness of Save Page WE for users who regularly work with pages containing expandable content.
Thank you for your hard work on this excellent tool, and I look forward to any improvements you might consider.
Best regards,
Pavel - 5 段階中 5 の評価Firefox ユーザー 18582702 によるレビュー (3ヶ月前)
- 5 段階中 5 の評価Firefox ユーザー 13462872 によるレビュー (4ヶ月前)
- As a regular user of Save Page WE, I appreciate its ability to save entire web pages as single HTML files, making subsequent editing straightforward. This functionality surpasses Firefox's standard save feature, offering more accurate archiving and easier modification of saved pages.
- 5 段階中 5 の評価Radioamatoro によるレビュー (5ヶ月前)
- 5 段階中 5 の評価Firefox ユーザー 18709981 によるレビュー (5ヶ月前)
- 5 段階中 5 の評価Firefox ユーザー 14295457 によるレビュー (6ヶ月前)
- 5 段階中 5 の評価Víctor A. Rodríguez (Bit-Man) によるレビュー (6ヶ月前)Great tool!
One single problem I have is not allowing to download www.google-analytics.com/analytics.js but entering it in my browser can be shown and downloaded - 5 段階中 5 の評価Firefox ユーザー 13545908 によるレビュー (7ヶ月前)
- 5 段階中 5 の評価Noel Miles によるレビュー (7ヶ月前)No doubt, the best offline page saver. Saved my fandom guide without effort and access it smootly without destroying the web. Thumbs up!
- 5 段階中 5 の評価Firefox ユーザー 18594010 によるレビュー (8ヶ月前)
- This was a huge help in saving some service manuals from my auto manufacturer that stopped offering PDF versions of their documents and because "normal saving" of the HTML through the web browser didn't preserve the page formatting, hyperlinks (within the same webpage), and images. I had a couple errors or incomplete saves at first, but the add-on configuration tip that popped up resolved them.
- 5 段階中 5 の評価Firefox ユーザー 14060941 によるレビュー (10ヶ月前)
- 5 段階中 4 の評価Firefox ユーザー 13560193 によるレビュー (10ヶ月前)