to Airbrake

Home → Suggestions →

More browser information for Javascript notifications

Jacob's Avatar

Jacob

10 Jun, 2011 03:17 PM

It would be nice to see which browsers are causing pain when using Javascript notifications. Right now it's hidden pretty deep down in the notification information. It makes it hard to figures out if a given error is only relevant for a specific browser or browser version. One of the issues is that it's very laborious to figure out which browsers are affected by a given notification if I have many instances of a single notification.

  1. 2 Posted by Harold Gimenez on 11 Jun, 2011 03:15 PM

    Harold Gimenez's Avatar

    Hi Jacob,

    Thanks for the suggestion. As we work to improve the javascript notifier and UI - currently experimental - we can take this into consideration as well. I agree, it seems like user browser should be front and center when dealing with javascript errors.

  2. Harold Gimenez closed this discussion on 11 Jun, 2011 03:15 PM.

Comments are currently closed for this discussion. You can start a new one.

2 people watching.

  • New Issue

  • Conversation Started

  • The discussion is closed

    No more actions from Airbrake or the discussion starter are required.

  • Re-open the discussion

Recent Discussions

18 Jun, 2013 09:59 PM Timeouts
16 Jun, 2013 04:09 PM No subject
12 Jun, 2013 11:30 PM time zone for times in notifications
12 Jun, 2013 10:22 PM Some information on the occurrence of this error is still being processed and is not yet available. This data may not processed due to invalid XML. See the knowledge base for more information.
12 Jun, 2013 11:36 PM exception_message is undefined, js error in notifier.js

Recent Articles

Adding Assembla Integration
Alternate Plugins, Widgets, Addons and Extras
Gitblame
Jira integration common issues
Installing Airbrake gem