Saving only the HTML works, "web page, complete" doesn't.
There's some issue with nsIWebBrowserPersist here. There's a `<script>` tag on the page that has a src of `//?loc=https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/` . That's a protocol-relative URL, but you can't do that without a hostname, so creating a URL fails, which throws an NS_ERROR_MALFORMED_URI which breaks the DOM walk at https://dxr.mozilla.org/mozilla-central/rev/7f816aa10a2053973c4e6977c5d6f6bf15f38820/dom/webbrowserpersist/WebBrowserPersistLocalDocument.cpp#1101-1104 . Tom's hardware can fix this by making the URL not broken, but obviously webbrowserpersist code shouldn't fail on this.
Moving to where the source code docs say bugs in this component should go.
Saving only the HTML works, "web page, complete" doesn't.
There's some issue with nsIWebBrowserPe rsist here. There's a `<script>` tag on the page that has a src of `//?loc=https:/ /forums. tomshardware. com/threads/ what-is- the-actually- difference- between- udimm-and- dimm.1575984/` . That's a protocol-relative URL, but you can't do that without a hostname, so creating a URL fails, which throws an NS_ERROR_ MALFORMED_ URI which breaks the DOM walk at https:/ /dxr.mozilla. org/mozilla- central/ rev/7f816aa10a2 053973c4e6977c5 d6f6bf15f38820/ dom/webbrowserp ersist/ WebBrowserPersi stLocalDocument .cpp#1101- 1104 . Tom's hardware can fix this by making the URL not broken, but obviously webbrowserpersist code shouldn't fail on this.
Moving to where the source code docs say bugs in this component should go.