ActiveX event handlers in an HTA using JScript

In C# I can write event handlers as follows:

var wdApp = new Microsoft.Office.Interop.Word.Application();
wdApp.DocumentBeforeSave += (Document doc, ref bool saveAsUI, ref bool cancel) => {
   //do stuff here
};

In VBA/VB6, I can use static event handling:

Dim WithEvents wdApp As Word.Application

Private Sub wdApp_DocumentBeforeSave(ByVal Doc As Document, SaveAsUI As Boolean, Cancel As Boolean)
    'do stuff here
End Sub

I would prefer to use dynamic event handling. However, in JScript, even when using static event handling with the syntax described here:

var wdApp = new ActiveXObject('Word.Application');
wdApp.Visible = true;

function wdApp::Quit() {
    window.alert('Quit');
};

it fails:

0x800a138f - JScript runtime error: Object expected

Also, static event handling is an option in VBA/VB6, because the declarations can be marked Private. However, in JScript, both the variable and the handler have to be declared in the global scope.

Two questions:

1. How can I handle events of Automation-created objects with JScript in an HTA environment? (Note: I know that it is possible in WSH using a prefix passed to CreateObject, and a function named wdApp_Quit, but I am looking for an HTA solution.)

2. How can I do this without polluting the global scope?

There is an older question here.

The error appears to be because

1. In Javascript/JScript function declarations are evaluated first, before the variable is initialized. It's as if the code was written thus:

    var wdApp;
    function wdApp::Quit() { ... }
    wdApp = new ActiveXObject('Word.Application');
   

2. The Microsoft JScript parser interprets the specially-named declaration (with ::) as an instruction to attach the function as an event handler.

3. But at the point of the declaration, the handler cannot be attached to the object referred to by wdApp, because wdApp at that point is still undefined. Hence, the error.

The solution is to force the function declaration to be evaluated after wdApp is initialized. This can be done in one of three ways¹:

1. Since the function declaration is hoisted only to within the function scope, wrap the function declaration in an IIFE:

    var wdApp = new ActiveXObject('Word.Application');
    (function() {
        function wdApp::Quit() {
            //do stuff here
        }
    })();
   

2. Create the declaration using some sort of string -> code mechanism -- eval, setTimeout with a string, window.execScript, or new Function:

    var wdApp = new ActiveXObject('Word.Application');
    eval('function wdApp::Quit() { ... }`);
   

3. Initialize the variable before the current SCRIPT block. Most of the examples in the Scripting Events article do this by setting the id property on some element before the SCRIPT block:

<object progid="ordersystem.clsorder" id="myorder" events="true"/>
<script language="jscript">
    function myorder::onNew() {
      WScript.Echo("new order received from myorder")
    }
//...

but this could also be done using multiple SCRIPT blocks:

    <SCRIPT>
        var wdApp = new ActiveXObject('Word.Application');
    </SCRIPT>
    <SCRIPT>
        function wdApp::Quit() {
            //do stuff here
        }
    </SCRIPT>

As far as polluting the global namespace, only the third variant requires wdApp to be in the global namespace; the other two variants can be wrapped in an IIFE.

^{1. Technically, there is a fourth way under IE and HTAs, but it involves non-standard HTML instead of non-standard Javascript; But it can only be used if the object is declared using the HTML OBJECT tag, not with new ActiveXObject( ... ).}

<script for="wdApp" event="Quit">
    //do stuff here
</script>