DOM renderer: direct attach these events

[wmertens]

What is it about?

event handling performance

What's the motivation for this proposal?

Adding on:mousemove means that the qwikloader queries window, document and every parent dom node from the current one whenever the mouse moves

Proposed Solution / Feature

So, let's make the DOM renderer attach direct listeners for:

Event	Why direct attachment is required
mousemove	Fires 60–1000+ times/sec. Delegation would invoke the walker on every move → CPU meltdown.
mouseover / mouseout	Same frequency issue + relatedTarget logic is fragile in delegation.
mouseenter / mouseleave	Do not bubble → delegation impossible.
wheel	Often needs passive: false for preventDefault(). Also high frequency.
scroll	High frequency + performance-critical (browser optimizes direct listeners).
touchmove	High frequency + usually needs passive: false to prevent scroll jank.
pointermove	Same as mousemove — too frequent.
drag	Continuous, high-frequency during drag.

and maybe manage qvisible too

One step further may be to automatically add a visibletask that does the attaching and loads the QRLs so the qwikloader can stop listening to them.

[wmertens]

let's first fix the qwikloader so it separately listens on window / document / elements