misleading comment in responsive special classes documentation
misleading comment in responsive special classes documentation
mnbob70
Posts: 19Questions: 2Answers: 0
Under special classes there is a comment for "never" that suggests the option is no longer needed because column visiblity provides the same functionality. Unless I'm mistaken, the comment is misleading because using visiblity works like "none" and still shows values in child rows. I was trying to figure out how to keep one column out of my modal and initially skipped using "never" because of the comment. IMO the comment should be moved to "none".
Replies
Good point! I think those names are actually rather confusing with how things work now. What I've just committed is to remove that extra bit of explanation from the
never(since it isn't correct!) and added this block after the class strings list:Many thanks for pointing this error out.
Allan
Just to be clear, am I correct that the only way to keep a value out of my modal when using tableAll to render all details is to use the "never" class?
Or, when you write "marked as hidden", is that a different setting than visible=false?
In other words
columns.visiblewould need a third state instead of just boolean true/false to completely use it in place of the pre-2.0 never class.No -
visible: falseis what I had intended with calling the column hidden. They are the same thing.So yes, if you want it in the table as visible, but not in the details view, use
never.Allan