You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Ilya Borisov (JIRA)" <ji...@apache.org> on 2017/11/13 06:21:00 UTC
[jira] [Created] (IGNITE-6873) Web console: some error messages are
too technical
Ilya Borisov created IGNITE-6873:
------------------------------------
Summary: 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: Ilya Borisov
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)