In brief: after updating to v148 on Firefox for Android, I can no longer select an existing destination folder when editing bookmarks.
To give a bit more detail: if I edit a bookmark or try to move it in any other way, when I am prompted to choose a destination I can only see and select the top-level "Bookmarks" folder, and not any of my already-made and previously used sub-folders. This, despite confirming that those sub-folders still exist because I can see them and navigate them in the non-editing bookmarks menu.
What happens is this:
- I edit a bookmark in the bookmarks menu (doesn't matter if it's a new or existing bookmark, and it doesn't matter if I use the three dot menu or if I press and hold and use the "Move" icon)
- When on the edit page, I see "Save in" at the bottom and click on the folder name there
- On the next menu that opens, I see the top-level "Bookmarks" folder with a checkbox and an expand carat; I *assume* I'm meant to press on the folder name or on the expand carat, and it would expand down to show all the subfolders, whence I could choose one. What *actually* happens is nothing -- the top level folder never expands, and thus I cannot select any other folder besides the top level "Bookmarks".
I can click on that expand carat all day and it never shows me any of the folders I've already set up and used thousands of times, not even if I make a new folder in the same session and try to move additonal bookmarks into that. It's as if the expand UI element itself is broken.
That probably sounds like a minor inconvenience, but as I mentioned I have thousands of bookmarks; I use my mobile browser to save interesting articles and science preprints as reference material for my writing, and I had an organization scheme that was working well up to now. I was planning to actually go through and re-organize these into smaller sub-folders by narrower topics, to make things easier on myself, but now I can't do that.
I've posted this issue to Mozilla support already and haven't yet heard any response (in fairness, it's only been a few days and I'm sure they're swamped).
In the meantime I was hoping someone here would at least have run into the same issue, maybe get some attention on the problem so that the devs can implement a fix if I'm lucky, or failing that hear if there's a known (non-power user) workaround already.
