If you confirm this is a bug of next.js, it’s meaningless to repost the same issue here. We cannot help you to fix an internal bug of Next.js while their contributors do

you can comment the issue that you reproduced the bug, you can react to it, make it more visible etc

rn 0 comments from next devs, this can't get lost in the issues tab because it's major

and it is a bug with next, look at src code, clearly not working as api docs say, and also they had the same bug some time ago (it was same thing but w/ position fixed: https://github.com/vercel/next.js/issues/47475) and tried fixing it: