Eric Vicenti raised the concern about how large query block hurt the performance of the document. I suggested the idea of limiting the query block to some bounded number of results and let it have an independent vertical scroll.

Eric asked what would happen if the user opens the document focused on a block bellow the query block and would scroll up. I said that nothing would happen as the results of the query block are embedded with a separate vertical scroll, and not "sewed into" the page itself.

To demonstrate what I mean I suggest looking at how Notion works with embedded databases. But instead of a vertical scroll, they have a "Load more" button bellow the database. This is arguably better, because having two containers with independent scrolls can be confusing and bad UX.

So, regardless of where you land in the document, the height of the query block is the same by default and it always starts at the beginning. I think this is a fair tradeoff, and tbh I have no other ideas on how to solve this.