HTML

Structure of content on the web

  • Web APIs

    Interfaces for building web applications

  • Learn
  • HTTP Observatory

    Scan a website for free

  • Web APIs
  • Window
  • Instance properties
    1. credentialless
    2. devicePixelRatio
    3. documentPictureInPicture
    4. event
    5. external
    6. fence
    7. fullScreen
    8. innerWidth
    9. launchQueue
    10. locationbar
    11. mozInnerScreenX
    12. mozInnerScreenY
    13. navigation
    14. orientation
    15. originAgentCluster
    16. performance
    17. screenLeft
    18. scrollbars
    19. scrollMaxX
    20. scrollMaxY
    21. sessionStorage
    22. sharedStorage
    23. status
    24. trustedTypes
    25. atob()
    26. back()
    27. blur()
    28. captureEvents()
    29. clearImmediate()
    30. confirm()
    31. dump()
    32. find()
    33. forward()
    34. getDefaultComputedStyle()
    35. getScreenDetails()
    36. moveTo()
    37. prompt()
    38. queryLocalFonts()
    39. releaseEvents()
    40. requestFileSystem()
    41. scroll()
    42. scrollByLines()
    43. scrollByPages()
    44. setImmediate()
    45. setResizable()
    46. showDirectoryPicker()
    47. showModalDialog()
    48. showOpenFilePicker()
    49. showSaveFilePicker()
    50. sizeToContent()
    51. webkitConvertPointFromNodeToPage()
    52. webkitConvertPointFromPageToNode()
  • Events
    1. beforeprint
    2. cut
    3. error
    4. hashchange
    5. messageerror
    6. orientationchange
    7. pageswap
    8. resize
    9. scrollsnapchange
    10. scrollsnapchanging
    11. unload
    12. vrdisplayactivate
    13. vrdisplayconnect
    14. vrdisplaydeactivate
    15. vrdisplaydisconnect
    16. vrdisplaypresentchange
  • Inheritance
    1. AbstractRange
    2. Comment
    3. DOMError
    4. DOMPoint
    5. Document
    6. Event
    7. MutationRecord
    8. NodeList
    9. Text
    10. TreeWalker
    11. Window interface may be used to report errors to the console or event handlers of global scopes, emulating an uncaught JavaScript exception.

      This feature is primarily intended for custom event-dispatching or callback-manipulating libraries. Libraries can use this feature to catch errors in callback code and re-throw them to the top level handler. This ensures that an exception in one callback will not prevent others from being handled, while at the same time ensuring that stack trace information is still readily available for debugging at the top level.

    • Syntax

    js
    reportError(throwable)

    Parameters

    throwable

    An error object such as a TypeError.

    Return value

    None (undefined).

    Exceptions

    TypeError

    The method is called without an error argument.

    Examples

    Feature test for the method using:

    js
    if (typeof window.reportError === "function") {
  / function is defined
}

    The following code shows how you might create and report an error, and how it may be caught using either the onerror event handler property or by adding a listener for the error event. Note that the handler assigned to onerror must return true to stop the event propagating further.

    js
    const newError = new Error("Some error message", "someFile.js", 11);
window.reportError(newError);

window.onerror = (message, source, lineno, colno, error) => {
  console.error(`message: ${error.message}, lineno: ${lineno}`);
  return true;
};

window.addEventListener("error", (error) => {
  console.error(error.filename);
});

/ Output
/ > "message:Some error message, lineno: 11"
/ > "someFile.js"

    Specifications

    Specification
    HTML
    # runtime-script-errors

    Browser compatibility

    BCD tables only load in the browser

    See also