Bug 1326511 - remove "supported browser" alert
Summary: remove "supported browser" alert
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-3.6.6
: 3.6.6.1
Assignee: Greg Sheremeta
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-12 20:55 UTC by Greg Sheremeta
Modified: 2016-05-25 16:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-25 16:30:46 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-3.6.z+
ylavi: planning_ack+
gshereme: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)
browser support (143.92 KB, image/png)
2016-04-22 18:50 UTC, Greg Sheremeta
no flags Details
updated site (177.02 KB, image/png)
2016-04-28 22:02 UTC, Greg Sheremeta
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 56653 0 master MERGED webadmin: remove 'unsupported browser' warning 2016-05-02 16:26:47 UTC
oVirt gerrit 56934 0 ovirt-engine-3.6 MERGED webadmin: remove 'unsupported browser' warning 2016-05-02 20:17:51 UTC
oVirt gerrit 56941 0 ovirt-engine-3.6.6 MERGED webadmin: remove 'unsupported browser' warning 2016-05-03 06:39:13 UTC

Description Greg Sheremeta 2016-04-12 20:55:22 UTC
Description of problem:
Browser support alert was implemented in webadmin header in Bug 1188229. We've had users confused by the message. Also, I personally find it very intrusive because I use Chrome and it pops up every time.

We only support Firefox ESR downstream. But for upstream, practically any modern browser will work fine. Certainly every modern Chrome works.

After discussing with Yaniv Kaul, he suggests completely disabling this message upstream and only enabling it downstream.

This is my suggestion too. I would like PM's thoughts.

Version-Release number of selected component (if applicable):
4.0

Expected results:
upstream = no compatibility message
downstream = has the message

Comment 1 Greg Sheremeta 2016-04-22 18:50:00 UTC
Even downstream, any modern browser will work fine. Let's remove the warning completely and follow these guidelines: https://access.redhat.com/help/browsers/

Comment 2 Greg Sheremeta 2016-04-22 18:50:29 UTC
Created attachment 1149884 [details]
browser support

Comment 3 Greg Sheremeta 2016-04-28 22:02:07 UTC
X-Ref: https://github.com/oVirt/ovirt-site/pull/219

Comment 4 Greg Sheremeta 2016-04-28 22:02:36 UTC
Created attachment 1152066 [details]
updated site

Comment 5 Vojtech Szocs 2016-05-02 18:00:57 UTC
(In reply to Greg Sheremeta from comment #1)
> Even downstream, any modern browser will work fine.

GWT compiler targets a limited set of user agents (browsers), for oVirt the current list is following:

- IE10 and better
- Firefox
- Chrome and Safari

Given that above are the mainstream browsers, I'm OK with removing the "browser unsupported" alert message in WebAdmin UI.

Comment 6 Vojtech Szocs 2016-05-02 18:02:45 UTC
> - IE10 and better
> - Firefox
> - Chrome and Safari

Forgot to mention, that ^^ should apply to oVirt 3.6 as well.

Comment 7 Petr Matyáš 2016-05-06 15:40:08 UTC
Should this message be displayed in RHEVM or not? Because the message is gone in both RHEVM 3.6 and oVirt 3.6 for all browsers I tried (Firefox 46, Chrome 50 and 52, Vivaldi 1.1)

ovirt-engine-3.6.7-0.0.master.20160506053801.gitee34ba4.el6.noarch
rhevm-3.6.6.2-0.1.el6.noarch

Comment 8 Greg Sheremeta 2016-05-06 15:42:39 UTC
See comment 1. It should be completely removed.

Comment 9 Petr Matyáš 2016-05-06 16:05:57 UTC
Yeah, in comment 1 is "completely disabling this message upstream and only enabling it downstream", that's the reason for my question, because that's not how it works now. In downstream (RHEVM) the message is not appearing as well, but according to comment 1 it should.

Comment 10 Greg Sheremeta 2016-05-06 16:13:53 UTC
Nah, comment 0 (original text) is that. Comment 1 changed it. Sorry for the confusion.

Comment 1 --> https://bugzilla.redhat.com/show_bug.cgi?id=1326511#c1

Please mark as verified. You're good.

Comment 11 Petr Matyáš 2016-05-07 09:19:41 UTC
OK, then this works as expected :)


Note You need to log in before you can comment on or make changes to this bug.