progressive-enhancement

Progressive enhancement - Node.js, Backbone.js

阅读更多关于 Progressive enhancement - Node.js, Backbone.js

问题 The node.js server has two roles: RESTFul API on routes with prefix /api Renders website pages on the others routes (/ /plans /features /terms ...) For the moment, all my pages render a "Loading page..." combined with the Backbone application that replaces the DOM when the Backbone.router starts. I would like to build the website pages server-side when an user reaches a page and let Backbone handles the next part of the navigation when the user navigates on the website. I know how to do it

Dropdowns with 10 thousand possible values and sequence-important dropdowns vs. graceful degredation

阅读更多关于 Dropdowns with 10 thousand possible values and sequence-important dropdowns vs. graceful degredation

问题 Background I have this form that uses javascript exclusively to search through ~5k entries (suppliers) and populate a select dropdown from them (factories, ~10k entries). Right now, it's a javascript-required form. I'd like to make it so that javascript errors no longer render the form unusable, but the number of entries and the sequential nature of the entries leave me without a idiomatic way to provide just a basic html version. The Issues Sequential/hierarchical dropdowns An example

Detect support for meta viewport scaling

阅读更多关于 Detect support for meta viewport scaling

问题 Is it possible to detect whether the browser will scale the website based on the meta viewport element? 回答1: There isn't any JavaScript method to detect if the meta viewport will be applied. However, you can check if it was applied via two step process with inline js in the head, with an approach such as: <head> <script> var clientWidth = document.documentElement.clientWidth; </script> <meta name="viewport" content="width=device-width,initial-scale=1"> <script> if (clientWidth !== document

Is progressive enhancement a current issue anymore?

阅读更多关于 Is progressive enhancement a current issue anymore?

问题 There are couple of things I hear in defense of progressive enhancement. Javascript is off or not available. According to W3School's Javascript statistics, 95% had Javascript enabled January 2008 (2.5 years ago). The trend, based on those stats, seems to be that Javascript enabled browsers are on the rise. Heavy AJAX adoption has probably pushed users to enable even faster. To support text-only or accessibility doesn't make a lot of sense from the business perspective since they probably

Designing a website for both javascript script support and not support

阅读更多关于 Designing a website for both javascript script support and not support

问题 Okay i know that it's important for your website to work fine with javascript disabled. In my opinion one way to start thinking about how to design such websites is to detect javascript at the homepage and if it's not enabled redirect to another version of website that does not javascript code and works with pure html (like gmail) Another method that i have in mind is that for example think of a X (close button) on a dialog box on a webpage. What if pressing the X without any javascript

Ajax fallback when Javascript is disabled

阅读更多关于 Ajax fallback when Javascript is disabled

问题 Problem: i) In a JSF2 application, I want to create a page with a tab control, where, when the user clicks on a tab, the contents for the panel below is loaded from an xhtml file in the server through an ajax call. ii) I want this to support graceful degradation (when Javascript is disabled), so that upon clicking the tab, an HTTP request is fired, and a new page is loaded...or the other way round, through progressive enhancement. Partial solutions: i) I guess I can accomplish this through

Are progressive enhancement and graceful degradation same thing, practically speaking?

阅读更多关于 Are progressive enhancement and graceful degradation same thing, practically speaking?

问题 Are progressive enhancement and graceful degradation basically the same thing? 回答1: Not quite. They tackle similar problems, but from different angles. "Graceful degradation" implies you have spiffy functionality, and can deal with it being less spiffy (but still need it to work somehow) in browsers that don't support it. "alt" attributes on images, and the <noscript> tag, are examples of this. "Progressive enhancement" implies you're starting out with just basic content, and want to add

How important do you think Progressive Enhancement is? [closed]

阅读更多关于 How important do you think Progressive Enhancement is? [closed]

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 7 years ago . Progressive Enhancement is a web development methodology that not only allows greater portability and accessibility but in my opinion,

Detect when JavaScript is disabled in ASP.NET

阅读更多关于 Detect when JavaScript is disabled in ASP.NET

问题 In the Render method of an ASP.NET web-control, I need to alter the output of the Html based on whether JavaScript is enabled or disabled on the clients browser, Does anyone know the right incantation to figure that out? 回答1: The problem with using script to check whether javascript is enabled is that you only find that out after the script hasn't run. Some solutions try the opposite - they use javascript to set a value and then supply Javascript enabled controls if that value is later

Are progressive enhancement and graceful degradation same thing, practically speaking?

阅读更多关于 Are progressive enhancement and graceful degradation same thing, practically speaking?

Are progressive enhancement and graceful degradation basically the same thing? Not quite. They tackle similar problems, but from different angles. "Graceful degradation" implies you have spiffy functionality, and can deal with it being less spiffy (but still need it to work somehow) in browsers that don't support it. "alt" attributes on images, and the <noscript> tag, are examples of this. "Progressive enhancement" implies you're starting out with just basic content, and want to add spiff for browsers that support it without breaking the site for those that don't. As an example of this,