Show incompatible browser warning

[sebastianbenz]

We should generate server-side a warning page for unsupported browsers based on user agent.

Context: #185

//cc @juliantoledo @adewale @kul3r4

[ithinkihaveacat]

Can amp-user-notification (or some minor variation thereof) be used for this? (I imagine we don't want to do anything too intrusive given that the AMP page in question is likely to mostly work.)

[sebastianbenz]

@ithinkihaveacat some older browsers (e.g IE9) won't show anything at all which makes it necessary to handle compatibility detection server-side anyway.

[ithinkihaveacat]

What will users see after they're redirected? Do they get redirected to the canonical page? Or an interstitial that lets them decide whether to proceed anyway and/or download a better browser? Where does the list of compatible UAs come from, and are web crawlers included?

I'm a bit wary of any change in behaviour that is dependent on UA. The approach has a somewhat chequered history technically, as is likely to be politically controversial way of dealing with old browsers.

On 13 Jun 2016, at 11:02, Sebastian Benz [email protected] wrote:

@ithinkihaveacat some older browsers (e.g IE9) won't show anything at all which makes handling it server-side necessary anyway.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.