[
https://issues.apache.org/jira/browse/IGNITE-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296201#comment-16296201
]
Ilya Borisov commented on IGNITE-6873:
--------------------------------------
[~pkonstantinov] how to test:
1. Open web console in Chrome.
2. Open Chrome Developer Tools.
3. Open "Network conditions" tab.
4. Change useragent, reload the page – you should see an "unsupported browser"
message if the browser is not in the supported list and no message for
supported browsers.
> 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
> Components: wizards
> Environment: Chrome 29
> Reporter: Ilya Borisov
> Assignee: Pavel Konstantinov
> 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)
