1174133 - Error objects should provide different fileName/columnNumber/lineNumber to different consumers

Status: NEW

(Core :: JavaScript Engine, defect)

Description

[Boris Zbarsky [:bzbarsky]]

Specifically, a content exception that got thrown from chrome code (e.g. via new contentWindow.Error) should show the content code that was on the stack at the time (if any) when viewed from content and the chrome code when viewed from chrome.  That's how DOMException works.

This probably requires making fileName/lineNumber/columnNumber accessors instead of slots and having them read from the saved stack if one is present instead of from the filename/line/column stored in the JSErrorReport.

It also requires at least fixing the self-hosting treatment in saved stacks (see bug 1173638 comment 1 item 1).

Comment 1

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

These properties are non-standard, right? Chrome doesn't have them. Therefore, there shouldn't be too many web compat issues, and we are free to change them to accessor properties without Breaking The Web?

Comment 2

[Jeff Walden [:Waldo]]

I doubt it'll be that easy, but feel free to try.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Didn't realize other UAs did not support these.

That does make it easier to do whatever the heck we want for now and then if people ever want to standardize these to push back on attempts to make them value props.