Comment 4 for bug 894143

It is still true with the git-master version (See attachment for version information)

I can fix it but would need a design decision.

At the moment the delete of a folder seems to only delete the folder entry in the database, leaving all its child entries orphaned.

For me this seems to be a bug as well. It would make the bookmark database grow infinitely.

The proper fix would probably be to implement a recursive delete.

One may not like such recursion and may want a confirmation message box to popup.

What would be the preferred behaviour?

1- recursively delete everything without message?
     After all the user knows what it does when he deletes a folder... (my choise.... it just does the asked job)
2- recursively delete non empty folders only after a user confirmation?
     with a confirmation message box poping up for each non empty folder,
     we can can have the options [Abort] [Yes for all] [No for all] [Yes] [No] in that case
3- do not delete non-empty folders?
     In that case we can keep the remaining folders in the selection
4- do as 3 with regular delete and as 1 with a Ctrl+<delete>?
     Probably a better choice than 1 but more difficult to "discover" for the user.