Move Link not working #54
Labels
No labels
bug
dependencies
documentation
duplicate
extension
feature request
fixed
frontend
good first issue
help wanted
improvement
invalid
investigating
javascript
planned
question
released
server
wontfix
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sofa/webcrate#54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🏷️ WebCrate Version
v1.4.2
⚙️ Environment
Chrome, Safari
🐞 Describe the bug
In a link detail 'box', selecting
Move Linkopens the window as expected, however clicking on the dropdown menu under the "Select a crate to move the link" button performs a quick animation, then returns to the main crate page without allowing for a selection to be made.As far as i recall, this worked prior to the update applied today.
📚 To Reproduce
Move Link💡 Expected behavior
a list of available crates should appear, from which a selection can be made.
📋 Additional context
No response
Hey, thanks for reporting this bug!
I encountered the issue as well, will fix it asap. It should work if you open the link as a page.
This feature actually only came with that update, it didn't exist before. Previously you could only move links by dragging and dropping them to another crate :)
Cool. Glad it wasn't just me. I'd initially placed the blame on Safari until it was repeatable in Brave (Chromium based).
Interesting bit of bias confirmation there! I was sure I'd moved via menu option in the past. Guess I would have just moved the card, which is what I ended up doing as a workaround anyhow.
Yeah, funny how the brain works sometimes 😅 Had a similar thing happen to me a while ago with another piece of software. Swear I had used a feature in the past, but they insisted it had never existed 😂
This issue has been resolved in version 1.4.3 🎉
@craigz refer to the docs on how you can update to the latest version :)
@BetaHuhn i've just updated and can confirm it's working!
Great! Thanks for confirming :)
Sorry that it took so long to fix, got busy with other projects :/