Platform-generated JavaScript errors should not be reported out to user code

Fixed Issue #10957024


Feb 14, 2017
This issue is public.
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

[Split from #8187485]

As a general rule, please consider any error without a proper line-number a serious offense. Supporting Edge is not a requirement for us right now, but we felt like being inclusive – but getting an error without a functioning line-number, that you can’t find using step-debugging, is an impossible to support situation in general. If you want developers to embrace Edge, please search for all places in your code base where these kind of error messages are outputted, and mark a big fat ‘TODO’ above it, to at least internally acknowledge that situation is far from optimal and some developer is taking the (way too easy) way out.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Jeff W.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “Fixed”

    You need to sign in to your Microsoft account to add a comment.

    Sign in