Bugs (regression): scroll in the Prisma Studio Page and save changes

[Rodaviva29]

I've updated my Prisma Studio Core to 0.27.3, to get the support for Dark mode, but while updating I got two bugs. I’m using Prisma Studio Embedded.

1. Now I can scroll a bit to the bottom for some reason;
2. I can't save changes that I made (nothing happens).

[Rodaviva29]

Hey @sorenbs, could this something I missed? Or some regressions of the update?

[sorenbs]

Hey there - can you try to take a look at pnpm demo:ppg. It will start a pglite database and run embedded studio in a thin shell. Can you reproduce the bug there?

If not, then this is an issue in how you are integrating embedded studio, and potentially something we should document better.

[Rodaviva29]

Hey there - can you try to take a look at pnpm demo:ppg. It will start a pglite database and run embedded studio in a thin shell. Can you reproduce the bug there?

If not, then this is an issue in how you are integrating embedded studio, and potentially something we should document better.

Hey, I still didn't test it, but I found a way to reproduce the second one!
When "infinite scroll" is enabled saving doesn't work. I disabled that new option and saved as normal :)

Regarding the first one, that weird scroll in excess didn't appear before.

[Rodaviva29]

Hey, have some updates and findings!

1. It only happens in "infinite scroll" when editing values that if the setting was off wouldn't show in the first page.
2. Regarding the weird scroll, it doesn't happen in the demo. But it didn't happen in the previous version still.

[sorenbs]

Hi @Rodaviva29 — your follow-up detail that it only happened for rows that wouldn't be on the first page was exactly the clue we needed, thank you. With infinite scroll on, the grid queries one growing window of rows, but the save/delete mutations were still scoped to the classic pagination pages — so edits to rows beyond the first 25 targeted a collection that didn't exist and silently failed. Fix is up in #1545, verified end-to-end in the demo.

The extra vertical scroll you mentioned didn't reproduce in the embedded demo shell (matching your own finding), so if it persists after this fix, could you open a separate issue with your embedding setup? Thanks again for the careful debugging.