In a list made before the checkbox change, or with a text copied from a list made before the checkbox change, with âShow checkbox in front of checklist parentâ turned OFF, toggle Make checklist on a parent. In the example below I do the toggle on âUteâ.
Firefox 69.0a1 nightly or Chrome 75.0.3770.100 on Windows 10.
Additional information
If I turn âShow checkbox in front of checklist parentâ ON, while the list is in the âmade checklistâ state, all items get checkboxes as expected. But if I then do âunmake checklistâ on âUteâ again I get this:
Sorry for the late reply⌠I tried a bunch of documents that existed before this change, both on the desktop app and the web app. Couldnât repro it.
It might be because âVindjackaâ and âUtebyxorâ are already set as checklist parents? Can you try toggling them again? Thatâs the only explanation I could think of that could cause this. If thatâs the case, itâs more of a transition issue than a bug (meaning if Dynalist were designed as the new version, this issue wonât happen). There were invisible states floating around that caused this.
You could enable the legacy mode to more clearly see which items previous had checkboxes in front of it.
I guess this can be fixed by changing thing around so that if a checklist parent doesnât have any children, it would show a checkbox?
I forgot to mention that my test case is like this:
Test
a
b
c
d
First, make âaâ and âdâ checklists. Then, make âTestâ a checklist. Youâll see that âaâ and âdâ still donât get their checkboxes.
As far as I can tell, Iâm having the same transition issue as mentioned above, and yes, your test case is in line with whatâs going on.
I realize that itâs not theoretically a bug, but I have such extensive list/checklists (discontinuous) that all got mixed up with the new checklist behavior, and unfortunately the easiest way of dealing with it is checking the setting for âshow checkbox in front of checklist parent.â It would just take too long to make and unmake all of the checklists in an order than keeps the boxes in the right places.
However, as the new behavior fails to meet my needs anyway, I donât feel so bad about having to stick with the old one. I followed the discussion and was looking forward to the change, but it didnât end up solving my issues with checklists in general. I appear to be in the minority that prefers more flexibility with toggling checklists (I would love to be able to toggle at will!) and likes to have bullet points nested under checklist items (like this guy). Still hoping for a way to make it work someday
Sorry for the late reply in turn, but Iâm in the same boat. Iâm happy with the old behavior, and the sudden change of the default way of handling checklists broke stuff for me. Itâs probably a transition problem, and as long as we can keep the old style if we want I wont be upset.
A gripe that I have with the new way is that I canât really see if an item is a âchecklist in waitingâ but with no children and therefore wonât get a checkbox (such as âdâ in the example above). Can probably be done with some CSS tweaking, but I stick to the old setting instead.
