UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. tar -xvf chrome-bug-reduced-test-case.tar.gz
2. serve the chrome-bug-reduced-test-case directory on localhost with a webserver
3. load page in chrome and compare the console output from clicking on the three buttons

What is the expected behavior?
DOMExceptions should have a "stack" property

What went wrong?
Uncaught exceptions caused by a DOMException (caught and handled via window.onerror) have a .stack property.

Unhandled promise rejections caused by a DOMException (caught and handled via window.onunhandledrejection) do not have a .stack property.

See attachment annotated screenshot for example output from the reduced test case.

The other attachment (not annotated) shows the async stacktrace where Chrome knows the original callsite of the promise that was eventually rejected.

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 63.0.3239.132  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 

Deleted: chrome-bug-reduced-test-case.tar.gz 869 bytes

chrome-bug-reduced-test-case.tar.gz 869 bytes Download

Deleted: annotated-screenshot.png 167 KB

	annotated-screenshot.png 167 KB View Download

Deleted: Screen Shot 2018-01-16 at 14.37.21.png 33.5 KB

	Screen Shot 2018-01-16 at 14.37.21.png 33.5 KB View Download