The three observers deliver in three different places in the event loop.
MutationObserver: a microtask. The first DOM change queues one mutation observer microtask; it runs at the next microtask checkpoint, when the current script, listener or callback returns to an empty stack. Rendering isn't involved, so it runs in hidden pages too. During a real click it runs between listeners; after el.click() it waits until the whole dispatch returns, as with any microtask.
ResizeObserver: inside the rendering update. After animation frame callbacks, the browser runs style and layout, then delivers resize observations, then repeats layout for any deeper elements those callbacks resized. All of that happens before paint, so a change made in the callback appears in the same frame. A microtask checkpoint follows each callback, so mutation observers triggered there run before the next observer.
IntersectionObserver: computed in the update, delivered as a task. After the resize loop, the browser computes intersections and queues one notify intersection observers task. That task runs after the update finishes, so after that frame is painted, and other tasks can run first. Changes made in an IntersectionObserver callback show in the next frame.
Initial notifications. ResizeObserver and IntersectionObserver deliver their first entries in the first rendering update after observe(). The IntersectionObserver spec stops the browser from skipping that update as unnecessary while a target still awaits its first entry. MutationObserver has no initial call.
Hidden pages get no rendering updates, or very few. In Chrome 156, a size change and an intersection change in a background tab produced no ResizeObserver or IntersectionObserver callback for 3 s; both arrived within 0.5 s of the tab becoming visible. Firefox 159 still ran 2 animation frames in those 3 s and delivered both in them. The MutationObserver callback ran immediately in both.