[jira] [Assigned] (IGNITE-6873) Web console: some error messages are too technical

["Ilya Borisov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ilya Borisov reassigned IGNITE-6873:
------------------------------------

    Assignee: Andrey Novikov  (was: Ilya Borisov)

[~anovikov], please review. I've decided to go with a second option. Supported browsers are as follows: IE11, Chrome last 18 months, Firefox last 18 months, Safari 10+, Edge last 6 months. IE11 and Safari choices are based on what I was told before as minimal supported versions. Chrome, Firefox and Edge have generally very lax requirements.

> Web console: some error messages are too technical
> --------------------------------------------------
>
>                 Key: IGNITE-6873
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6873
>             Project: Ignite
>          Issue Type: Improvement
>      Security Level: Public(Viewable by anyone) 
>          Components: wizards
>         Environment: Chrome 29
>            Reporter: Ilya Borisov
>            Assignee: Andrey Novikov
>            Priority: Minor
>
> *What happens:*
> Chrome 29 throws an error about missing {{atob}} and {{btoa}} global functions (used in the frontend AgentManager service). The error gets succesfully displayed to user in a default error notification, but ambiguous message "Reference error: can't find atob" provides very little useful info for most of users without advanced JS background.
> *What should happen:*
> Web console should relay this and similar errors in a more accessible manner.
> *Possible solutions:*
> 1. Consider missing API errors as operational, add explicit handler to generate better messages, detect features and polyfill when possible. Pros: better UX, increases supported browsers percentage. Cons: very high maintenance cost.
> 2. Notify user about unsupported/outdated browser. Pros: easy to implement, simultaneously covers lots of potential issues. Cons: very non-specific, UX worse than option #1.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)