@unknown Definitely related and maybe the same issue, I'm not sure.
Still an issue in 1.21.
The cause of this bug seems to be that items popping out of frames are always given a set velocity upwards. So when frames are under a block they get sent into that block and flung out randomly.
This mechanic is especially frustrating with item frames underwater because items are given a velocity upwards combined with the buoyancy of items means they always go rocketing towards the surface. Imgur video of the problem
Can confirm in 1.21
I don't think this should necessarily be changed because it would break all the farms that use water to break and collect crop drops. Maybe it should change path/farmland to dirt if there is a water source block above, but not if it's flowing water. Alternatively, make them behave similarly to grass blocks but with a delay. After 30 seconds underwater, they start converting to dirt so farms can still use water collection systems but farmland/paths wont persist underwater indefinitely.
Related to this: You can't create farmland/paths underwater with their respective tools. It seems to check if the block above the dirt block is air, and if true: it converts, false: it does nothing. So even though water doesn't crush path/farmland like all other blocks, it still blocks the conversion. If farmland/paths are allowed underwater, you should be able to create them underwater but if they aren't going to be allowed underwater then the current implementation makes sense. I can make a separate issue for this specifically but the logic seems to be heavily intertwined with any decisions made around this so I thought I would leave it here as a comment.
@Jiingy My bad. I have reproduced it in vanilla 1.20.6 and posted an updated imgur video. All the mods I run are creative utility/convenience so I didn't really think about them but I should have spun up a vanilla instance anyway.
Can confirm in snapshot 24w13a.
@MrMuskle Why is that ticket resolved? Is it intended that frogs jump onto rails or was it just intended that they are allowed to jump over rails? Was there some explanation on that report but it got lost in the migration? I didn’t search closed tickets because it’s still a bug happening in the game and now my ticket is also closed but I have no idea why this isn’t considered a bug. I find this kinda frustrating.
Direct link to the ticket for convenience