Issues

Known Issues

All browsers

• A page in the extension store and some browser vendor related sites cannot be captured, due to a security restriction. (see this question for details)
• A page with invalid HTML (usually generated by scripts) may be altered when the captured page is opened. See this issue for details.
• The actual content of a resource cannot be captured if the href attribute of the <base> element of the owner document has been changed after the resource had been loaded.
• The current content of an embedded page via <object> or <embed> element cannot be captured (automatically fallback to capture source).
• The current content of a frame page using data: protocol cannot be captured (automatically fallback to capture source). See related issue reports for Chromium and Firefox.
• The image representation of a canvas drawn based on cross-site data cannot be captured, due to a security restriction.
• The image representation of a canvas drawn using certain advanced techniques cannot be completely captured if the buffer has been cleared.
• A streamed video (usually presented as a <video> with blob: protocol) cannot be captured.
• save used for fonts or style images may fail to capture some referenced fonts or style images when the web page indirectly references some fonts or CSS animinations using CSS variables. See this issue for details.
• The captured scripts may not work as in the original web site even if scripts are configured to be saved due to a change of the environment. (see this question for details)
• A blob that is revoked after loaded by a script cannot be captured.
• A font that is dynamically loaded by a script cannot be captured.
• A stylesheet injected by another browser extension cannot be captured. This could cause an issue like ads hidden by an ad-blocker extension be still visible in the captured page.
• When performing a capture selection with selecting an element in a shadow DOM, the captured range will be expanded to the outermost shadow host element.
• Only a path under the default downloading folder can be specified as the folder to save scrapbook data. (see this question for details)
• The resources referenced by the content erased by the page editor cannot be captured.
• The content of a frame cannot be reliably recovered after it or its parent element has been removed from DOM using the undo or revert erase functionality of the editor.
• Annotation tools do not work inside a shadow DOM.
• Scripts cannot run in a web page opened by the archive page viewer, due to a security restriction.

Google Chrome (or most Chromium-based browsers)

• When capturing as single HTML, links or redirections to a resource file (which can exist when capturing a file or capturing linked files) will be blocked by the browser due to security restriction. (Can be workaround via opening in a new tab or manually pasting the link in the address bar)
• Checking Ask where to save each file before downloading browser setting causes every pending saved file be prompted for confirmation. This issue has been raised in 2014, but regarded as a normal behavior by the developers and not yet considered a subject to fix. (not for Microsoft Edge)
• When saving to the scrapbook folder, downloading of certain files (such as *.js or *.exe) may be considered unsafe and blocked by the browser, and a confirmation for each file is required for them to be downloaded.
• When saving to the scrapbook folder, certain chars may be forcefully replaced by the browser (e.g. % be replaced with _).

Firefox (or most Firefox-based browsers)

• Capturing a page in a non-default container is disallowed due to a compatibility concern. See this issue for details.
• The content of a sandboxed frame (<iframe sandbox="...">) cannot be captured (will fallback to capture source content). See this issue for details. (for Firefox < 128)
• A page opened with file: protocol cannot be captured. See this issue for details.
• A page opened with file: protocol cannot be viewed with the archive page viewer.
• The switch of scrapbooks in the search page may be rendered badly in Windows. See this issue for details.

Kiwi Browser (or Chromium-based browsers on Android)

• A downloading error always happens when Save captured data to: is Scrapbook folder and Save captured data as: is Folder, since the browser doesn't support creating a sub-folder under the default download folder.

Firefox for Android

• Capturing a private tab may cause an unexpected error or inconsistency, as the browser extension cannot open a private tab. (for Firefox for Android < 79)
• A download always fails when Save captured data to: is Scrapbook folder, since the browser doesn't support downloads API. (for Firefox for Android ≥ 79)