I think some can fail due to the removal of goToItem.

Yep, was for that.

looks slick! I really like how you put the input field inline replacing the button. This looks great!

was the intention for removing goToItem so it doesn't move the user to the folder after creation? I can help update the tests to expect that if you want to remove that functionality

was the intention for removing goToItem so it doesn't move the user to the folder after creation? I can help update the tests to expect that if you want to remove that functionality

Yup, in new folder and file creation. And I would appreciate your help, I'm not familiar with the tests yet.

I'll do a commit removing it again.

Thanks! And now is better with the button in notifications :)

Btw, don't merge the PR yet, I'll a validation for check if folders with the same name exist.

I've changed the close hovers in ReplaceRename.vue so that way if a conflict happen when copying or moving you're still in the copyMove prompt clicking "cancel", but doesn't look great after that:

The fix for this is remove the loading spinner (which also hide the buttons), but I want to ask first if you're ok with removing it 😅

Another bug is that if you click "replace" in the ReplaceRename prompt, the item becomes corrupted with 0.0b of size.

I don't think that the code here can be causing that, so maybe is a backend issue (?)

I can't replicate the corrupted issue when I try to replace works as expected. does this happen all the time?

Yep, every time. Not just here, in stable too.

oh replacing its own file with itself?

Yeah replacing with itself should be possible, let me check on that.

should be good to go from my perspective!

Yup! To me too, you can merge it.

Btw, I want to ask something... Why you always remove the border-radius from plyr, is intentional? I just want to know 😅
Because that makes the audio player square.

because you can see the border radius on videos doesn't go to the edges. you see the radius clip the video corners a little bit.