3 ms·
If half my resources aren't loading, or aren't loading in full, despite all the fallbacks built into HTTP itself to avoid precisely that scenario, there's no fa
by mantrax4 13y ago
If half my resources aren't loading, or aren't loading in full, despite all the fallbacks built into HTTP itself to avoid precisely that scenario, there's no fallback on Earth that can work around this.
If my JS would load in half, my no-JS form might also load in half, what do we do now. Have a fallback where we accept the form in pieces?
As for people who have a "personal preference", well, they might as well have a personal preference to browse the web via telnet. It's their problem.
The requirement to use a full, working web browser to browse a web page is hardly extreme.
- oneeyedpigeon 13y agoLet's say your JS is hosted on a different domain from your html (quite a common scenario) and that domain can't be reached (for any of the many possible reasons). Or a bug is introduced into the javascript (which happens a lot). In each case, your approach results in a broken page, whilst a fallback approach still works perfectly. Re: personal preference - have you never heard the saying 'the customer is always right'? No business in its right mind would purposefully turn down money from a bunch of its customers just because they happen to have a personal preference which can easily be accommodated. Note that a web browser without javascript support doesn't fail to be a 'working browser' just because you say so. Note that I am not saying you must do this on your personal blog, or that Javascript isn't a very useful feature of today's modern browsers. Just that it's good engineering practice to be inclusive and to handle exceptions gracefully.