runScripts: 'dangerously' changes the output of Object.getOwnPropertyNames(jsdom.window)

[DanKaplanSES]

Basic info:

• Node.js version: 20.10.0
• jsdom version: 24.0.0 (I saw no difference in v22)

Minimal reproduction case

import { JSDOM } from 'jsdom';

const { window } = new JSDOM('', {
    url: 'http://localhost',
    runScripts: 'dangerously',
    resources: 'usable',
    pretendToBeVisual: true,
})

console.log(`Object.getOwnPropertyNames(window).filter((k) => k === "HTMLElement").length`, 
    Object.getOwnPropertyNames(window).filter((k) => k === "HTMLElement").length); // 0

How does similar code behave in browsers?

console.log(`Object.getOwnPropertyNames(window).filter((k) => k === "HTMLElement").length`, 
    Object.getOwnPropertyNames(window).filter((k) => k === "HTMLElement").length); // 1

Additional information

1. I've yet to understand why, but the runScripts: 'dangerously', is causing this problem. When I comment that out, the console.log prints 1, just like a browser.

2. I created this StackOverflow question before creating this issue. It might provide some helpful context, and it includes additional log statements showing similarities between the two environments. For example, window.HTMLElement have equivalent property descriptors in both.

   I don't fully understand the ramifications of these differences, but it made it challenging to troubleshoot the JSDOM error I was experiencing at the bottom of that SO example.

3. I tested this in Firefox and Google Chrome and both print 1.