It isn't static html, it is an ever changing tapestry of js fetching this and that, on demand loaded content, and so on. To archive, one need to not only snag the page, and loaf time js, but also js triggered by user actions.
This means you need to load the whole page, then hit js triggered by page load, etc, then save output to html.
Because, some of those js libs won't work in future browsers, others won't work if they can't phone home, or 100 other things.
Archive.org is about 100 years from now too, and js content is a PITA in that respect.
This means you need to load the whole page, then hit js triggered by page load, etc, then save output to html.
Because, some of those js libs won't work in future browsers, others won't work if they can't phone home, or 100 other things.
Archive.org is about 100 years from now too, and js content is a PITA in that respect.