Skip to content
This repository has been archived by the owner on Dec 13, 2020. It is now read-only.

inform users that only Chrome is currently supported on login screen #594

Closed
metasnw opened this issue Mar 29, 2017 · 4 comments
Closed

Comments

@metasnw
Copy link
Member

metasnw commented Mar 29, 2017

Type of issue

Feature request

Current behavior

you can log in with any browser
problem is that most testing is done on chrome at the moment and other browsers might not work

Expected behavior

if user does not have supported chrome version he gets a message on login screen which informs him about that his browser might not be fully supported

Steps to reproduce

@Dunkat Dunkat self-assigned this Mar 30, 2017
@damianprzygodzki
Copy link
Contributor

damianprzygodzki commented Mar 30, 2017

In my opinion it is not good to inform user that app is working only on chrome. I believe that on the other platforms it is working as well.

All of the dependencies we are using, are supporting most of modern browsers, and while development, im using also firefox and safari, to test things.

This limitation in my opinion is too drastic.

I would like more to inform user when he using some unsupported browser.

@Dunkat Dunkat removed their assignment Mar 30, 2017
@cadavre
Copy link
Contributor

cadavre commented Mar 30, 2017

he gets a message on login screen which informs him about that his browser might not be fully supported

So I believe it's actually only about a small message on login screen.

One way or another, afaik, we're testing not only in Chrome, but also Firefox and Safari. I think it would be better to gather feedback about other browsers and also adapt them, Chrome isn't 100% market.

@cadavre
Copy link
Contributor

cadavre commented Apr 4, 2017

"Your browser might not be fully supported.\n
Please try Chrome in case of any errors."

Dunkat added a commit that referenced this issue Apr 4, 2017
Dunkat added a commit that referenced this issue Apr 4, 2017
damianprzygodzki added a commit that referenced this issue Apr 5, 2017
inform users that only Chrome is currently supported on login screen #594
metas-ts added a commit to metasfresh/metasfresh that referenced this issue Apr 5, 2017
[#1267](#1267) Cannot open ASI editor in Swing
[#277](metasfresh/metasfresh-webui-api-legacy#277) Don't export JSONDocument.fields if empty
[#597](metasfresh/metasfresh-webui-frontend-legacy#597) cancel on "Do you really want to leave?" sends you 2 steps back
[#595](metasfresh/metasfresh-webui-frontend-legacy#595) kpi disappears when minimize
[#594](metasfresh/metasfresh-webui-frontend-legacy#594) inform users that only Chrome is currently supported on login screen
[#1222](#1222) Show orderline description only in the first column of the Jasper
[#541](metasfresh/metasfresh-webui-frontend-legacy#541) Hide new and delete included documents when they are not available.
Dunkat added a commit that referenced this issue Apr 7, 2017
damianprzygodzki added a commit that referenced this issue Apr 7, 2017
Fix errors on safari and opera #594
@metas-dh
Copy link
Member

Results of IT1
tested with w101 on Firefox

  • try logging in: msg for user "Your browser might be not fully supported. Please try Chrome in case of any errors." is displayed underneath Login: OK

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

6 participants