3 ms·
I think my render in Chrome is pretty broken. Here's a screenshot of the top of the page: https://drive.google.com/open?id=1YVtcV-J0JrDyW2pJ6vwgEDsgjOEusyEH htt
by buchanae 8y ago
I think my render in Chrome is pretty broken. Here's a screenshot of the top of the page: https://drive.google.com/open?id=1YVtcV-J0JrDyW2pJ6vwgEDsgjOEusyEH https://drive.google.com/open?id=1YVtcV-J0JrDyW2pJ6vwgEDsgjO...
- RomainGuy 8y agoLooks like the page wasn't able to load all of its resources. Try to refresh the page until it works. I should make an offline version that doesn't require online processing.
- mkl 8y agoIt took multiple reloads for it to work for me on Android Chrome, and was almost unreadable for a couple of minutes (MathJax processing? Tried KaTeX?) due to an enormous right margin. The margin and font(?) changed multiple times. Is there a PDF version?
- tripzilch 8y agoSort of! The document uses a JS tool called MarkDeep to convert extended MarkDown into styled HTML. Just look at the source, it's 99% plaintext Markdown. If you read the MarkDeep docs, you'll find that it has a feature to convert the source into PDF instead. I admit I haven't tried this, though. If it were up to me, I'd do the transform offline and just serve the static HTML instead. And sure, a link to the PDF just to be nice :)
- RomainGuy 8y agoWe just serve straight from the source tree so it's not out of date :)
- robocat 8y agoMaybe add onerror tags to JavaScript and CSS resources and show a warning if something fails to load? Why is it still so hard to design a page to load reliably?
- buchanae 8y agoI made an offline version by opening it in Firefox and printing to PDF. Seems to look fine.