2 Matching Annotations
  1. Oct 2015
  2. code.google.com code.google.com
    Issue 357568 - chromium - Extension errors should trigger the global onerror event. - An open-source project to help move the web forward. - Google Project Hosting
    2
    1. robertknight 22 Oct 2015
      The temporary solution we found is to wrap chrome.* api callback with setTimeout() function. In that case errors thrown within chrome.* api call are passed to window.onerror with correct line number. Example:

      Wrapping all the chrome.* async API calls such that exceptions in the callback result in an error being logged to a handler that we control looks like the way to go.

      chrome-extension-development
    2. robertknight 22 Oct 2015

      In Chrome extensions, errors thrown in callbacks for async APIs do not trigger the global window.onerror handler.

      chrome-extension-development
    Visit annotations in context

    Tags

    Annotators

    URL

    code.google.com/p/chromium/issues/detail