Page MenuHomePhabricator

Deal with some browsers providing less details for JS error logging
Open, NormalPublic

Description

Depending on the browser version and the logging method (onerror vs try...catch), some or all of the line, column or stack information might be missing.

  • handle different names / locations accross browsers (e.g. e.line in Safari vs. e.lineNumber in Firefox vs. line number available via e.stack in Chrome)
  • walk call stack on IE to recreate the stack (see Errorception blog post)
  • research if there are similar workarounds for other browsers (another handy blog post)

If window.onerror limitations turn out to be unsurmountable, T513 could be an alternative.

Event Timeline

Tgr created this task.Sep 29 2014, 11:18 PM
Tgr claimed this task.
Tgr raised the priority of this task from to Normal.
Tgr updated the task description. (Show Details)
Tgr changed Security from none to None.
Tgr added a subscriber: Tgr.
Tgr updated the task description. (Show Details)Sep 29 2014, 11:29 PM
Tgr removed a subscriber: Unknown Object (MLST).
Tgr updated the task description. (Show Details)Oct 1 2014, 10:10 AM
Tgr renamed this task from Deal with some browsers providing less error details to Deal with some browsers providing less details for JS error logging.Oct 1 2014, 10:15 AM
Tgr updated the task description. (Show Details)
Tgr removed Tgr as the assignee of this task.Jan 30 2015, 2:38 AM
Jdforrester-WMF moved this task from Untriaged to Backlog on the Multimedia board.Sep 4 2015, 6:41 PM
Restricted Application added subscribers: Matanya, Aklapper. · View Herald TranscriptSep 4 2015, 6:41 PM