Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat are people doing about browser degradation and HTML5
    primarykey
    data
    text
    <p>I am in the process of updating my business website and I've decided to use HTML5/CSS3 (with some PHP) for the whole thing and it works fantastic in every new browser (IE9, FF6, O11, S5, C13) with or without JS.</p> <p>Now I am not sure what I should do about every other browser version. I imagine I have a small amount of leeway with most of the browsers (atleast the previous version) except IE8 (I have the IE shiv, but it doesn't cover non-js browsers.). Most of the features degrade nicely, but there will always be issues with older browsers.</p> <ul> <li><p><em>I know nonJS browsers are probably a minority, but it would be nice to cover them as well</em></p></li> <li><p><em>This list is ordered in the order of current preference to cover the largest number of browsers(nonJS/JS) but time to implement hasn't been considered.</em></p></li> <li><p><em>Only considering web-browsers, plan is for a mobile site for mobile browsers</em></p> <p>Here is the list:</p> <ol> <li><p>Build a really dodge version of the site using tables^, etc. and redirect the users there if they have an old version of the browser (server-side) and have a warning on there about upgrading.</p></li> <li><p>Use Javascript to fix up the bits they don't work (like the shiv). This doesn't really cover the nonJS browsers which as stated are probably a minority.</p></li> <li><p>Build a static old browser page to redirect the old browser users to a page with links to upgrade download links. This is a real copout solutions, but is quick to implement</p></li> <li><p>Assume the only users that have old browsers are IE users, and use conditional comments to implement one of the previous options. <strong>Assumptions are always bad</strong></p></li> <li><p>Pretend users have the most upto date browsers and make no attempt to fix the site at all. <strong>Not really a practical option</strong></p></li> <li><p>Rebuild the website for HTML4 and use it accross the site. <strong>Bit of a waste of current work. As well as it looks a bit dissappointing if a webdeveloper has a site using old technologies, which was the driving force for the upgrade</strong></p></li> </ol></li> </ul> <p>What are your thoughts/solutions to the HTML4/5 limbo? Is there anything you've done in current projects to combat this?</p> <p>Cheers,</p> <p>Steve.</p> <p>P.S. Being a member of the 'I hate IE6 and don't care for it's existance' club, I'm pretending that IE6 (or less) never existed.</p> <p><strong>Update (to clarify)</strong></p> <p>^ - by tables, I mean are really slapped together version of the current website, using either a table/non-table based layout. But something that may not look pretty when the source is viewed, it's really just there to fill the compatibility void.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload