41–50 of 353 posts
Please make your stuff work without JavaScript. This is a simple text-only web page (in courier new ffs) and it refuses to load with JavaScript disabled. There is no valid reason for this.
> Here is my plea: when you build hardware/software, please make it support the primitive, simple case.
I hate smart TVs with a burning passion. They accomplish literally the bare minimum to keep people happy and sometimes not even that. Samsung’s Tizen OS is the most genuinely frustrating experience I’ve had with a consumer device outside of printing. Advertisements on my home screen that can’t be disabled, dubious privacy, bugs that require me to reboot my TV, and of course security so bad that they recommend install…
Can't you just remove the smart TV's internet access (no wifi pw, no Ethernet) and treat it as dumb? Then attach a Chromecast or whatever "smart" dongle you think has the best UI.
drag mp4 to browser then cast it?
Earlier quoted context omitted.
Yeah, same here with JS. Solid black page, no content. View source indicates about half is some Google analytics boilerplate, the other half is a body consisting entirely of non-functional JS pulls. OP, where is the content stored?
https://raw.githubusercontent.com/anderspitman/anderspitman.... Note for OP: The reason this breaks without Javascript is because it's rendering the Markdown clientside. That could be moved to part of the build process without increasing your hosting requirements at all. I can see that you already have https://github.com/anderspitman/anderspitman.net/blob/master... started, so I'm assuming you know this already and t…
Irony: blank page w/o JS, fails in Outline.com.
Is this rendering Markdown to HTML on the fly in my web browser? Just render the markdown to HTML once on the server and upload it for the love of God. That being said, the article is entirely correct.
Because then when you edit the markdown you have to take an additional step.
Says the one who can't have a simple HTTP only site and I had to enable JS on NoScript in order to read his rant.
Earlier quoted context omitted.
https://raw.githubusercontent.com/anderspitman/anderspitman.... Note for OP: The reason this breaks without Javascript is because it's rendering the Markdown clientside. That could be moved to part of the build process without increasing your hosting requirements at all. I can see that you already have https://github.com/anderspitman/anderspitman.net/blob/master... started, so I'm assuming you know this already and t…
Rendering markdown client-side seems like a fine way to implement a web page. It's a cheap transformation, and it means you don't need any sort of server-side build process. Yes, some people choose to browse with JS disabled, but anyone who browses that way should expect that many sites won't work and will need to be manually whitelisted.
OP is already using a server-side build process to generate the static site. Inserting the HTML at the same time they built the site would add very little extra code to their build process, and nothing to their static hosting requirements.
If nothing else, would OP consider inserting a tag in each generated index.html that linked to the raw Markdown in their Github repo?