Hi Solly, You are right with your questions about user setting custom UA on their browser. And during my discussion with other Horizon community members on IRC, we decided that Horizon should not care about user setting custom UA on for their browser because it is not our job to identify that and fix. If user is setting custom UA for their browser which means they want that irrespective of the outcome.
Also we discussed about using Modernizr and also implementing graceful degradation but this will work for bigger features like canvas or svg but smaller css feature where it is breaking in older versions of IE like IE <9, will be a huge change and I personally think will be waste of resources and will make the code more complicated. Instead Horizon guys came to an conclusion that we will identify the browser type and version to deal with legacy browsers like older IE or firefox or any other browser and for other major features we can use feature detection with Modernizr. We are targeting all major browsers which are listed in this page - https://wiki.openstack.org/wiki/Horizon/BrowserSupport And I also think by going with this approach we will minimize the code complexity and also this small feature will greatly improve the UX experience for the end-users. Thank you for the reply and your views. Also can I put the contents of your reply as a comment into the Blueprint page? Because I think many others will also have same kind of questions. Thanks & Regards, Nikunj -----Original Message----- From: Solly Ross [mailto:sr...@redhat.com] Sent: Tuesday, October 14, 2014 9:37 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [horizon]Blueprint- showing a small message to the user for browser incompatibility I'm not sure User Agent detection is the best way to go. Suppose you do UA sniffing and say "show the message unless the UA is one of X". Then, if there's a browser which fully supports your feature set, but doesn't have a known UA (or someone set a custom UA on their browser), the message will still show, which could be confusing to users. On the other hand, if you do UA sniffing and say "show the message if the UA is one of X", then a browser that didn't support the features, but didn't have a matching User Agent, wouldn't show the message. If you go with User Agent sniffing, I'd say the latter way (a blacklist) preferable, since it's probably easier to come up with currently unsupported browsers than it is to predict future browsers. Have you identified which specific browser features are needed? You could use Modernizr and then warn if the requisite feature set it not implemented. This way, you simply check for the feature set required. Best Regards, Solly Ross ----- Original Message ----- > From: "Nikunj Aggarwal" <nikunj.aggar...@hp.com> > To: openstack-dev@lists.openstack.org > Sent: Tuesday, October 14, 2014 4:53:42 AM > Subject: [openstack-dev] [horizon]Blueprint- showing a small message > to the user for browser incompatibility > > > > Hi Everyone, > > > > I have submitted a blueprint which targets the issues end-users are > faces when they are using Horizon in the old browsers. So, this > blueprint targets to overcome this problem by showing a small message > on the Horizon login page. > > > > I urge to all the Horizon community to take a look and share your views. > > > > https://blueprints.launchpad.net/horizon/+spec/detecting-browser > > > > > > > > Regards, > Nikunj > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
