Please see the video below. Whenever I have a collection with in-line editing enabled, the data entry/updating experience is so incredibly glitchy. The first 10 seconds start out okay, but watch the full video below.
I don’t believe this has anything to do with my browser/computer as this has been the case ever since I’ve started using in-line editing for collections in Noloco (months). As I type, I’ll automatically exit the editing window, or once I finish entering data, it’ll revert to its previous value, or it’ll be a partial/skewed value, etc. Weird behaviors that make it very cumbersome to edit collection records.
5 Likes
I think I added feedback on this before there was the live community (just slack) but this seemed to be the best place for it
I’ll +1 the Glitchyness of the in line editing for a collection when it isn’t on a base record details.
It’s clunky UX for users so I often try to avoid it if at all possible.
Wasn’t able to avoid it with a client recently and today they asked why they have to do the check mark to save it.
It is a confusing ux for users especially since on base record details pages they can just type in directly and it saves. They don’t understand why there would be any reason for those to be different.
I understand it’s likely a tech build aspect of things that isn’t easy to just switch, but from a users non-technical experience it doesn’t make sense that they have one ability in one section of an app but not the same user behavior in another 
3 Likes
Glad you brought this back up, it’s consistently an issue for me
1 Like