The proposal for adding an additional option bag to ECMAScript Error constructor to construct errors with a cause property has reached stage 3 in the TC39 proposal process. The proposal is seeking for chaining logically related errors without losing their context information like messages, properties, and stacks.

There are discussions that DOMException can also adopt the signature (by overloading the second parameter name to with an object as the option bag) so that DOMException on the Web and Error in ECMAScript can be constructed with similar parameters.

As the proposal error cause has reached stage 3 and implementations have been trying to land the proposal (chakra-core/ChakraCore@b992a5d, WebKit/WebKit@b03c4f4), I'm opening this issue here seeking feedbacks on the DOMException changes.