Open tdammers opened 5 years ago
My blog is rendered in the browser with Markdeep, so to get pretty graphics it is, sadly, necessary to run JS. However, the fallback should be to show the source markup which should be almost as readable (if not as pretty). Maybe this is broken; I will investigate.
An even better alternative is to run the markdeep code once on my computer and publish the resulting (static) HTML, but so far my efforts in this have failed.
On Tue, Jan 08, 2019 at 01:17:17AM -0800, Emil Ernerfeldt wrote:
My blog is rendered in the browser with Markdeep, so to get pretty graphics it is, sadly, necessary to run JS. However, the fallback should be to show the source markup which should be almost as readable (if not as pretty). Maybe this is broken; I will investigate.
Hmm, I didn't see anything at all, just a white screen. I have some things whitelisted in NoScript, so it's possible that it would work in a clean block-everything configuration.
An even better alternative is to run the markdeep code once on my computer and publish the resulting (static) HTML, but so far my efforts in this have failed.
Ah, I see... there are plenty of markdown converters that can be used offline, but this one seems to be quite tied into the browser DOM.
-- Tobias Dammers - tdammers@gmail.com
Great article. Tried to show it to a friend, but it's pretty much illegible without javascript and they have vision difficulties. You may want to consider accessibility and fix it to work so everyone can read it.
Just a heads up; the page white-screens when JS is disabled or blocked. Looking at the page, however, this seems absurdly unnecessary, at least I can't think of a technical reason for this.