Minor Description
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.