Timeline for Should I provide fallbacks for HTML5/CSS3 elements in a web page at this point?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Jun 29, 2012 at 7:34 | vote | accept | Abluescarab | ||
| Jun 29, 2012 at 5:23 | answer | added | Juha Untinen | timeline score: 1 | |
| Jun 29, 2012 at 4:33 | history | edited | Abluescarab | Added programming-practices tag | |
| Jun 29, 2012 at 4:28 | comment | added | Abluescarab | @ClintNash From what I'm seeing, "progressive enhancement" is the concept of supporting older browsers while still using cool new features. So providing "fallbacks" for older browsers, even ones rarely used (such as IE6 and etc.) is still a good idea? I've been doing it up to this point, but it was just getting tedious, hence the question. | |
| Jun 29, 2012 at 4:18 | comment | added | Jack Stone | A topic that would be relevant for review would be progressive enhancement. | |
| Jun 29, 2012 at 3:34 | history | asked | Abluescarab | CC BY-SA 3.0 |