https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33568
--- Comment #74 from Tomás Cohen Arazi <[email protected]> --- (In reply to Katrin Fischer from comment #73) > I see what you mean, but we need to test this maybe - it can "blow up" the > table quite a bit. thinking of the notes fields (materials, internal note, > OPAC note, enumchron...) that you would want to see when set and not hide > via column settings by default. > > For libraries with only a few items per record, this could be seen as quite > a regression. Would it be possible to only "activate" this behavior if we > have a paged items table? Like check the count of items and then behave > differently? (just brainstorming, we need to decide on something, I am aware) I've been thinking about it, and maybe what we need is some sort of hint/tooltip that displays some of that info? So they can safely hide the columns entirely, but still know there's some extra info. Trying to see from another angle to unlock this. I get it. I understand your concern, but it is too tiny compared to the benefits having this in master will bring. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
