Interface: PointerLike

Defined in: telemetry.ts:44

The structural shape we need from a PointerEvent. Declared structurally, not as PointerEvent, so layer 1 stays free of the DOM and tests can hand us a plain object — which matters more than usual here, because jsdom's PointerEvent does not carry these fields at all.

Properties

altitudeAngle?

optional altitudeAngle?: number

Defined in: telemetry.ts:52

---

azimuthAngle?

optional azimuthAngle?: number

Defined in: telemetry.ts:53

---

clientX

clientX: number

Defined in: telemetry.ts:45

---

clientY

clientY: number

Defined in: telemetry.ts:46

---

getCoalescedEvents?

optional getCoalescedEvents?: () => unknown[]

Defined in: telemetry.ts:64

The two Pointer Events extensions, probed for EXISTENCE (never called here). Whether the API is present is a different question from whether it returned anything, and conflating them is how you misread a coalescing ratio of 1.00: it means "we saw one sample per event", which is a catastrophe if the API is missing and a non-event if the API is there and simply had nothing to batch.

Returns

unknown[]

---

getPredictedEvents?

optional getPredictedEvents?: () => unknown[]

Defined in: telemetry.ts:65

Returns

unknown[]

---

height?

optional height?: number

Defined in: telemetry.ts:56

---

pointerType

pointerType: string

Defined in: telemetry.ts:49

---

pressure

pressure: number

Defined in: telemetry.ts:48

---

tiltX?

optional tiltX?: number

Defined in: telemetry.ts:50

---

tiltY?

optional tiltY?: number

Defined in: telemetry.ts:51

---

timeStamp

timeStamp: number

Defined in: telemetry.ts:47

---

twist?

optional twist?: number

Defined in: telemetry.ts:54

---

width?

optional width?: number

Defined in: telemetry.ts:55