Show message in dashboard when browser's not compatible

[myleshorton]

Just IE7 to start. Would be great to link to the appropriate download as well. At this point probably IE 9, but it should be relatively easy to support Safari and link to that. Not sure that's actually better than IE 9 in any useful way to us though.

I also think this should correspond with making a call to the new error API along with the browser version so we know what's happening in the wild. Difficult to detect this on the backend unfortunately -- much easier from JavaScript I think.

[myleshorton]

This is clearly related to #59. I could easily detect the IE version from the installer. I think the problem, though, @pants is that the main option at that point would be to prompt the user to upgrade IE and to link to the site. That gets weird with the install sequence though -- I'd worry they would go and download it, install it, and then never make it back to our installer. I think it might be better to prompt them from the dashboard when they've already fully invested in Lantern, and I think it's easier and more maintainable there too. Either way would certainly work though. What do you think @forkner? My vote is to detect this in the dashboard and close #59.

[forkner]

I agree. I think it's fine to issue from the dashboard (and even eventually handle installing chrome or something from within lantern). If we have complex stuff to do on the system, I'd prefer it was built into "lantern itself" unless the installer software can already do it for free (in part to mitigate the cost of switching installer-builders). It seems fairly common to bootstrap with an installer and then receive necessary components as a part of the initial run.

I think we should keep some bug open for embedding/installing a compatible browser eventually though.

[lanterndev]

as of d72be14, here's what you get when you hit the dashboard using IE9's IE7 emulation:

The upgrade link points to http://www.beautyoftheweb.com/Experience#/download, which looks like it detects the best download given the user's system.

Also uses the new error API to notify the backend of the unsupported browser. Call is made every time the dashboard is loaded. Worth trying to avoid redundant calls?

[myleshorton]

Sweet! Will that appear on every page, or just the first? Also within the dashboard itself if they manage to get that far?

[lanterndev]

remains stuck to the bottom of the screen no matter what else is on it.

[lanterndev]

btw, when i went through the setup screens in IE7 clicking finish took me back to the start. didn't investigate what's going on since we're not officially supporting IE < 8. worth trying to make it work though?

[lanterndev]

meant to ask, i'm seeing the backend log the error API call, but i'm not seeing it show up in exceptional. any idea why?

[myleshorton]

It doesn't log anything if we're running from the dev version -- that's probably it.

[myleshorton]

I wouldn't worry too much about the IE7 cyclical screens issue at this point...slippery slope..

[lanterndev]

word! closing then.