ocular rewritten

My browser / operating system: Windows NT 10.0, Chrome 111.0.0.0, No Flash version detected

For whatever reason, if you have a sprite with a long page of scripts vertically, dragged blocks will be misplaced to be higher than they should be. This could cause problems since if you scroll down far enough, dragged blocks will appear to attach to the top of other blocks when they should attach to the bottom, or appear as if they'll attach to the bottom of a block when it's too far away. This looks to be a visual bug and it doesn't affect the dark gray silhouette of the dragged block when attaching it.

This happens in Edge as well, while it's absent in Firefox.

(Had an image prepared, but the host I used isn't supported)

For the image, try using cubeupload.

My browser / operating system: Android Linux 7.1.1, Chrome 111.0.0.0, No Flash version detected

Anyways, I have never experienced the problem myself AND I usually never have a long page.

Script length seems to be irrelevant. Just the page length. Unless that's what you meant?


Here, I'm dragging the show block to attach to the bottom of the go to random position block. The silhouette is where it should be, but the block itself is way too high to suggest that it'll attach there. It looks like it should attach to the top instead.

This is an exaggerated example since I'm using a sprite with a very long script page for the picture, but it starts to be noticeable after around 200 blocks worth of space downward from the top.

It's not just blocks either, variables and anything else that's draggable are affected too.

(Thanks for the host recommendation)

Ok, status update: I found out that my scale was set to 125% in my system settings by default. That seems to be the culprit since after changing it to be 100%, dragged elements no longer become offset upwards no matter how far down the page you are from the top.

So I guess this doesn't really count as a bug since you have to change something in your system settings to a different variable in order for this to even happen.


Short version: It's because my window scale setting wasn't 100%.