Discussion tracking: Event dispatching / listening between AFFINE and Blocksuite

[thorseraq]

AFFINE uses blocksuite as the EditorProvider. When reading the code of AFFINE (of the pathfinder branch), I met a question that when window dispatches an event, (the Capture phrase is disabled by default) this event bubbles up from the "window" element, which element will receive this event? (window seems don't have any parent element) .

I referred Bubbling and capturing explained.

In the bubbling phase, the exact opposite of the capturing phase occurs:
The browser checks to see if the direct parent of the clicked element has a click event handler registered on it for the bubbling phase, and runs it if so.
Then it moves on to the next immediate ancestor element and does the same thing, then the next one, and so on until it reaches the element.

[thorseraq]

It seems that the <editor-container></editor-container> added an event listener to window, but "this" remains referring to the<editor-container></editor-container>itself in the event handler (utilized arrow function)

[thorseraq]

After discussions with main maintainers (@colelawrence @doodlewind ), this turns out to be a workaround for now (As window exists in browser context, so components in whatever framework (Blocksuite uses Lit, AFFINE uses react) can add an event listener on it or dispatch an event on it. ), and @doodlewind suggests that a new comprehensive API design about how to reuse EditorContainer is welcomed.

[lawvs]

I met a question that when window dispatches an event, (the Capture phrase is disabled by default) this event bubbles up from the "window" element, which element will receive this event? (window seems don't have any parent element) .

You can read the DOM spec for a more detailed explanation. The parent of the window is null and the event will stop bubbling.

https://dom.spec.whatwg.org/#dispatching-events

Each EventTarget object also has an associated get the parent algorithm, which takes an event event, and returns an EventTarget object. Unless specified otherwise it returns null.

Nodes, shadow roots, and documents override the get the parent algorithm.

https://dom.spec.whatwg.org/#get-the-parent

[thorseraq]

thanks, It's very detailed, covering even situation of Nodes, shadow roots (Occasionally understand more about event bubbling rules)