59 bytes, text/x-review-board-request
Hey Morgan, any chance you could take a look at this? Thanks!
Promoting to blocker, as this is continuously spamming the browser console, which makes following the console a lot harder.
Severity: normal → blocker
I'm guessing the issue is that `errorMessageName` is only supplied for some subset of JS errors (instead of all possible script errors), so DevTools should check for a value first before logging a probe?
While fixing this, can the 'empty key' error message start including which histogram this is related to? It would help for debugging purposes.
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #6) > While fixing this, can the 'empty key' error message start including which > histogram this is related to? It would help for debugging purposes. This bug is only about the DevTools probe that triggered most of this errors, not the actual verification code that logged the errors. Anyway, your suggestion makes sense to me, so I copied it to bug 1334469.
Assignee: nobody → alessio.placitelli
Priority: -- → P1
Whiteboard: [measurement:client:tracking] → [measurement:client]
Attachment #8857520 - Flags: review?(bgrinstead) → review+
You need to log in before you can comment on or make changes to this bug.