General javascript error tracking

5 posts, 0 answers
  1. Thomas
    Thomas avatar
    143 posts
    Member since:
    Feb 2007

    Posted 05 Feb 2008 Link to this post

    I'm currently developing an large application that makes judicious use of Telerik controls most of which at this point are Prometheus controls. One problem I am seeing on a regular basis are javascript errors which then halt all further javascript on a given page. Obviously, my team and I are working on resolving these issues as much as possible. For example, we abandoned all use of the AJAX control toolkit controls so that we are only using standard ASP.NET controls or Telerik controls and preferably Prometheus controls to mitigate the sources of javascript.

    However, I see a serious support problem when I get ready to deploy. I will have no information about when and what error occurred if it is in javascript. If an error occurs on the server, I get a full stack trace and the user gets a clear indication that something went wrong. When it occurs in javascript, I get no information that an error occurred and the user has to be watchful for small error icons in their browser to note that a javascript error has occurred.

  2. Nikolay
    Admin
    Nikolay avatar
    3997 posts

    Posted 08 Feb 2008 Link to this post

    Hi Thomas,

    Some of our Prometheus controls provide client-side events that are fired if certain JS errors appear. For example - the combobox provides the OnClientCallbackError event, whereas the treeview provides OnClientNodePopulationFailed event. These events fire when the items/nodes failed to be populated using callback requests.

    Which are the JS errors you are talking about and which of our controls cause them?

    Greetings,
    Nick
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Thomas
    Thomas avatar
    143 posts
    Member since:
    Feb 2007

    Posted 08 Feb 2008 Link to this post

    The problems I am worried about generally do not stem from custom javascript written by our developers. As newer builds have been posted, the number of errors of have dropped. Generally, we have gotten two types of javascript errors:

    1. "h is not a constructor" error which I have seen much less of.

    2. "Parameter is not a type." I'm not sure if this is the exact error message. When I encounter it again, I'll post it.

    I'm more concerned with things like Norton Security and other security products perhaps creating issues with compression or Ajax ability or what have you, causing a javascript error to occur and we never getting any information about what happened or even that something did happen.
  5. Nikolay
    Admin
    Nikolay avatar
    3997 posts

    Posted 11 Feb 2008 Link to this post

    Hi Thomas,

    Is it acceptable for you to prepare a small and running project for us, where we can observe these errors? You can zip the files and attach the zip file to a new support thread.

    Regards,
    Nick
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  6. Thomas
    Thomas avatar
    143 posts
    Member since:
    Feb 2007

    Posted 11 Feb 2008 Link to this post

    I do not think you understand. I am not currently encountering a repeatable error for which I can provide the steps to reproduce. The Prometheus controls have been generally stable and more so as new builds become available.

    My concern is that in general if an error occurs on the javascript side of a control, I have no way of knowing that the error occurred or any information about the error. The user has to be particularly attentive in noticing that a javascript error has occurred, has to know what that means, must relay the information about what they were doing and must restart their browser or at least navigate to a simpler page to clear the error. That is a lot of burden to put on users.
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017