graceful-degradation

How to write backwards compatible HTML5?

99封情书 提交于 2019-11-28 21:28:35
I'd like to start using HTML5's basic features, but at the same time, keep my code backwards compatible with older browsers (graceful degradation). For instance, I'd like to use the cool CSS3 properties for making rounded corners. Is there any available tutorial for writing gracefully degradable HTML5 ? Additionally, what browsers should I support so that my app. is functional for at least 95% of visitors? What are the ways to test those browsers painlessly ? Sarfraz When talking about HTML5 or CSS3, you should head over to: When can I use... As can be seen, we are still far far away from

What is the difference between Progressive Enhancement and Graceful Degradation?

五迷三道 提交于 2019-11-28 15:42:44
I'm confused on what the difference is between Progressive Enhancement and Graceful Degradation . To me they seem like the same thing. Can you please explain to me the differences between the two and in which situation I would use one over the other? Alex Mcp They ARE almost exactly the same thing, but they differ in context. There is a class of browsers called "A Grade Browsers". These are your typical audience members that (probably) make up the majority of your visitors. You'll start with a baseline of these users. Call this best modern practices . If you want to enhance the experience for

How Does Rails 3's “data-method='delete'” Degrade Gracefully?

回眸只為那壹抹淺笑 提交于 2019-11-28 06:13:22
Rails 3 does some cool stuff to make Javascript unobtrusive, so they've done things like this: = link_to "Logout", user_session_path, :method => :delete ..converts to <a href="/logout" data-method="delete" rel="nofollow">Logout</a> But it just occurred to me.. When I turn off javascript the method isn't DELETE anymore, it's GET as expected. So are there plans to, or is there some way to, allow these data- attributes to degrade gracefully, so that link still is a DELETE request? The change they made in Rails 3 with these data- attributes wasn't about graceful degradation, it was about

Python: Pickling a dict with some unpicklable items

别等时光非礼了梦想. 提交于 2019-11-27 17:52:46
问题 I have an object gui_project which has an attribute .namespace , which is a namespace dict. (i.e. a dict from strings to objects.) (This is used in an IDE-like program to let the user define his own object in a Python shell.) I want to pickle this gui_project , along with the namespace. Problem is, some objects in the namespace (i.e. values of the .namespace dict) are not picklable objects. For example, some of them refer to wxPython widgets. I'd like to filter out the unpicklable objects,

How Does Rails 3's “data-method='delete'” Degrade Gracefully?

China☆狼群 提交于 2019-11-27 01:14:10
问题 Rails 3 does some cool stuff to make Javascript unobtrusive, so they've done things like this: = link_to "Logout", user_session_path, :method => :delete ..converts to <a href="/logout" data-method="delete" rel="nofollow">Logout</a> But it just occurred to me.. When I turn off javascript the method isn't DELETE anymore, it's GET as expected. So are there plans to, or is there some way to, allow these data- attributes to degrade gracefully, so that link still is a DELETE request? 回答1: The

Best way to detect that HTML5 <canvas> is not supported

喜欢而已 提交于 2019-11-26 04:05:23
问题 The standard way to deal with situations where the browser does not support the HTML5 <canvas> tag is to embed some fallback content like: <canvas>Your browser doesn\'t support \"canvas\".</canvas> But the rest of the page remains the same, which may be inappropriate or misleading. I\'d like some way of detecting canvas non-support so that I can present the rest of my page accordingly. What would you recommend? 回答1: This is the technique used in Modernizr and basically every other library