it does seem to be positioned incorrectly
doesnt seem to happen anymore
it still exists
never mind
I couldnt recreate it, might’ve been an internal api issue
it does seem to be positioned incorrectly