computations created outside a `createRoot` or `render` will never be disposed

Escaping reactivity contexts is presumably usually because of async operations.

Well, I create this effect inside an event handler. My component is attached to a specific part of the DOM, creating a small island of reactivity. However the event in question is a

keydown

keydown

event attached to the document.

onMount(() => {
    document.addEventListener('keydown', kbHandler)
})

onCleanup(() => {
    document.removeEventListener('keydown', kbHandler)
})

onMount(() => {
    document.addEventListener('keydown', kbHandler)
})

onCleanup(() => {
    document.removeEventListener('keydown', kbHandler)
})

a) Is this the cause of the warning or am I mistaken?
b) What is a good way to do this?

Docs talk about delegated events that are attached to the document, but dispatched to the element (uncessary in this case, but whatever).

But I tried

<div onKeyDown={kbHandler}>

<div onKeyDown={kbHandler}>

and it won't fire my handler.

SolidJS•2y ago•

46 replies

martixy

computations created outside a `createRoot` or `render` will never be disposed

keydown

keydown

event attached to the document.

onMount(() => {
    document.addEventListener('keydown', kbHandler)
})

onCleanup(() => {
    document.removeEventListener('keydown', kbHandler)
})

onMount(() => {
    document.addEventListener('keydown', kbHandler)
})

onCleanup(() => {
    document.removeEventListener('keydown', kbHandler)
})

<div onKeyDown={kbHandler}>

<div onKeyDown={kbHandler}>

and it won't fire my handler.

computations created outside a `createRoot` or `render` will never be disposed

Similar Threads

computations created outside a `createRoot` or `render` will never be disposed

Similar Threads

Similar Threads

Similar Threads