Skip to content
This repository has been archived by the owner on Nov 26, 2018. It is now read-only.

A user should be able to user any browser of their choice #92

Open
brandonarbiter opened this issue May 8, 2014 · 2 comments
Open

A user should be able to user any browser of their choice #92

brandonarbiter opened this issue May 8, 2014 · 2 comments

Comments

@brandonarbiter
Copy link
Member

Currently, there are browser incompatibility issues with Blip. Users should be able to interact with Blip in the browser of their choice.

This is related to Hub #91

@cheddar @jebeck @HowardLook

@nicolashery
Copy link

Yes this is important, however browser support is something that needs to be carefully thought about, as it can be a lot of work supporting legacy browsers. I tend to say the latest "evergreen" (browsers that auto-update themselves) are best for modern web apps, else you can waste a lot of time. Need to be especially careful with IE, I think IE 10 started to be good but before it's kind of a pain... :)

Also, we agreed that for pilot we target Chrome only right? Just double-checking...

@brandonarbiter
Copy link
Member Author

Yes, only Chrome for Pilot. This is a backlog issue to make sure we do come
back and address browser support more thoroughly in the future.

In the meantime, thanks for contributing your thoughts around evergreen.
That's exactly what the issue is for - collect individual thought
contributions until the issue becomes a priority.

Brandon Arbiter
VP, Product and Business Development

*Tidepool *An open source, not-for-profit effort to build an open data
platform and better applications that reduce the burden of Type 1 Diabetes
and accelerate the commercialization of closed-loop systems.

Phone : 917 536 0505
*Email : *brandon@tidepool.org
*Web : *Tidepool.org http://tidepool.org/

On Thu, May 8, 2014 at 1:06 PM, Nicolas Hery notifications@gh.neting.ccwrote:

Yes this is important, however browser support is something that needs to
be carefully thought about, as it can be a lot of work supporting legacy
browsers. I tend to say the latest "evergreen" (browsers that auto-update
themselves) are best for modern web apps, else you can waste a lot of time.
Need to be especially careful with IE, I think IE 10 started to be good but
before it's kind of a pain... :)

Also, we agreed that for pilot we target Chrome only right? Just
double-checking...


Reply to this email directly or view it on GitHubhttps://github.com//issues/92#issuecomment-42576745
.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants