I think I replied in comment 13. We can surely implement a cleanup task, and we'll do in the future, but it would run delayed (once a week or less) and won't save the user from a crash. Thus, I don't think it's a good solution. Instead what we could do is when in the Places menu code we hit a symlink to a folder, we check ancestor menus. If it is linking to a folder that is also an ancestor, we just skip it. There are certainly better visual solutions but supposing in the future we implement the cleanup task, those will be removed anyway, so not rendering them should be fine.
Bug 1631239 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think I replied in comment 13. We can surely implement a cleanup task, and we'll do in the future, but it would run delayed (once a week or less) and won't save the user from a crash/hang. Thus, I don't think it's a good solution. Instead what we could do is when in the Places menu code we hit a symlink to a folder, we check ancestor menus. If it is linking to a folder that is also an ancestor, we just skip it. There are certainly better visual solutions but supposing in the future we implement the cleanup task, those will be removed anyway, so not rendering them should be fine.