@shida Thanks for fixing that. I still have some questions about the new ācollapsed item with no childrenā behavior Iām seeing (repro steps here: Collapsing item on mobile not getting synced to web).
This new behavior manifests when you add the first child to an item with no children that was previously in a collapsed state before its last child was removed, using either of these two methods:
- Zoom into the item and add the first child.
- Add the first child via API (e.g. Quick Dynalist).
Previously an item with no children was always considered uncollapsed, so adding the first child would have it remain uncollapsed. With the new behavior the previously collapsed item becomes collapsed when the first child is added using these two methods, but is uncollapsed if added by hitting āEnterā and indenting.
Was this change intentional? Itās slightly confusing from a usability perspective that the collapse state is sticky, as thereās no way to tell the difference between childless items that are ācollapsedā and ones that are āuncollapsedā.
Overall Iām fine with this new behavior as it fits in with how I use collapsed items + API, but I just wanted to make sure that this change was intentional.
Also, do you have an ETA for when the Android app will be updated? Since the Android app does not exhibit this behavior yet itās now sometimes uncollapsed even when itās collapsed on all other clients which is kind of annoying.