Been using this in nursing school - a lot of our content is done on horribly designed websites, and it's pretty common to hit submit and...... Naw it didn't take: all your shit just disappeared.
So, save with single file first, then submit, and if it fucks up then I've got a backup to copy and paste a replacement out of.
This is probably the best solution I've found so far.
Unfortunately, even this is no match for the user-hostile design of, say, Microsoft Copilot, because it hides content that is scrolled off screen so it's invisible in the output. That's no fault of this extension. It actually DOES capture the data. It's not the extension's fault that the web site intentionally obscures itself. Funnily enough, if I open the resulting html file in Lynx, I can read the hidden text, no problem. LOL.
Actually that might not have been done to deliberately disrupt your flow. Culling elements that are outside of the viewport is a technique used to reduce the amount of memory the browser consumes.
Yeah I tried readeck and while it does better than the others it still doesn't use single file (or I missed some configuration?)
I do like it because it even transcribes YouTube videos and that's very neat ! However, I work lot on superuser, stack*,ask* pages which aren't properly scraped and render with their comments.
The only perfect working solution I found was singlefile + Zotero.