#722@minor: Add timeStamp property to Event.

[aripalo]

Fix #722 by implementing timeStamp property on Event.

According to specification (see MDN and Spec) the timeStamp property is described as follows:

This value is the number of milliseconds elapsed from the beginning of the time origin until the event was created. If the global object is Window, the time origin is the moment the user clicked on the link, or the script that initiated the loading of the document. In a worker, the time origin is the moment of creation of the worker.

My proposed solution is to use performance.timeOrigin as the time origin to resolve the relative Event timeStamp value.

[capricorn86]

Nice contribution ⭐ Found some minor things.

[aripalo]

I had to do a little bit of "massaging" for the timeStamp test to work. Used this solution from StackOverflow.

There's still some other tests failing in my fork after merging the upstream changes (bringing in Turborepo etc), but I'll try to figure them out.

[aripalo]

I'm a bit stuck as now there's a circular dependency apparently due to use of performance 🤔

 FAIL  test/nodes/html-element/HTMLElement.test.ts
  ● Test suite failed to run

    TypeError: Converting circular structure to JSON
        --> starting at object with constructor 'HTMLDocument'
        |     property 'childNodes' -> object with constructor 'Array'
        |     index 0 -> object with constructor 'DocumentType'
        --- property 'ownerDocument' closes the circle
        at stringify (<anonymous>)

      at messageParent (../../node_modules/jest-worker/build/workers/messageParent.js:29:19)

I'll need to investigate this more a bit later.

[capricorn86]

I'm a bit stuck as now there's a circular dependency apparently due to use of performance thinking

 FAIL  test/nodes/html-element/HTMLElement.test.ts
  ● Test suite failed to run

    TypeError: Converting circular structure to JSON
        --> starting at object with constructor 'HTMLDocument'
        |     property 'childNodes' -> object with constructor 'Array'
        |     index 0 -> object with constructor 'DocumentType'
        --- property 'ownerDocument' closes the circle
        at stringify (<anonymous>)

      at messageParent (../../node_modules/jest-worker/build/workers/messageParent.js:29:19)

I'll need to investigate this more a bit later.

@aripalo usually this happens when toEqual() is used on a DOM element when it doesn't match. Then Jest is trying to convert the DOM element to JSON, but as DOM elements have circular references it fails.

I have tried to solve this in multiple places by changing from toEqual() to:
expect(element === otherElement).toBe(true)

I will try to make a better solution in the future. Maybe use Vitest instead and perhaps create a custom toEqual().

[capricorn86]

@aripalo I managed to find the problem with the failing unit test now. I have fixed it and pushed in two commits. I accidentally used the wrong user. It became a generated user, but I guess it is fine 😅

[aripalo]

@capricorn86 sweet! I was a bit stuck with this as I'm not really familiar with internals of Happy DOM and haven't had the time to dive into it lately.

Thanks for merging! 🙌 (and thanks for this library, really great stuff!)