Re: Re: phpsadness - P.C. shmee seee.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11-06-05 07:28 PM, Richard Quadling wrote:
On 5 June 2011 19:15, Robert Cummings<robert@xxxxxxxxxxxxx>  wrote:
2 words... progressive enhancement. If your browser doesn't support a
feature then it should degrade gracefully. Accessible web philosophy 101. I
hate going on to some website, especially government, and finding that it
sniffs my browser and then completely excludes me if it doesn't like what it
finds.

There is another approach. Regressive Enhancement.

Essentially, create your site with all the bells and whistles enabled.
Make full use of all / any standards compliant feature.

For browsers not capable of supporting that, use emulation techniques.

Sitepoint have a blog about this technique :
http://blogs.sitepoint.com/regressive-enhancement-with-modernizr-and-yepnope/

From my cursory read... regressive enhancement would need to rely on progressive enhancement to work :) If there's no JavaScript to do the lifting, then how can you regress?

An interesting read all the same. It's kind of like the compatibility layer PEAR releases for older versions of PHP so they have access to newer functions and stuff but implemented in PHP rather than C.

Cheers,
Rob.
--
E-Mail Disclaimer: Information contained in this message and any
attached documents is considered confidential and legally protected.
This message is intended solely for the addressee(s). Disclosure,
copying, and distribution are prohibited unless authorized.

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux