haha it's no worries! it might be a positioning issue on my end because i think i just have the return button layered directly on top of the other back button, so it's possible that you somehow managed to access the original back button instead of the return one. it's a shortcut i took that's apparently not as flawless as originally thought, so thank you for bringing it up regardless :)