You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
edit_biblio, for example, gets really wide and unwieldy. We might use another approach there or at least find a way to keep the help documentation visible while you scroll.
The text was updated successfully, but these errors were encountered:
Looking into this today, it seems like handsontables does some behind the scenes work that makes it a bit trickier than just setting a CSS for the table.
We can turn off AutoColumnSize by passing colWidths = '100px' (for example) to rhandsontable::rhandsontable. I think it would be preferable to leave it dynamic with the caveat of limiting a maximum width, but unfortunately that does not seem possible at the moment (see here).
I haven't been able to work around handsontable to set a maximum width when we are editing a cell (css handsontableInput).
One challenge I'm noticing with a fixed colWidths is if your columns are filled with lots of text, the horizontal scrollbar gets lost at the bottom of the page..
I opened a PR with the colWidths approach for you to test if you'd like (#113)
Another totally alternative idea I had was essentially transposing the CSV to scroll vertically through the different fields - this might actually be an easier way to visualize and input the data. Would just require more data manipulation.
edit_biblio
, for example, gets really wide and unwieldy. We might use another approach there or at least find a way to keep the help documentation visible while you scroll.The text was updated successfully, but these errors were encountered: