-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node-red-node-ui-table column width incorrect at random #81
Comments
Hi. Can you please share a minimal flow (use with nodes for data) that demonstrates this problem. Thanks |
Sure :) I hope this is what you have in mind, otherwise please tell me what else I can provide :)
|
I experienced the same problem and went to absolute width (defined interactive, stored in content and replayed via msg.uicontrol) You are not the only one: I believe the issue is related to the |
@Christian-Me : Thanks for the tip! I changed it to fixed pixel values and now it seems to work. Was a bit tricky thou to find out the right values to fill the whole space and don't get any scroll bars. |
Sure it is more difficult than percent values and there are improvements around this issue in later versions of tabulator. But until we manage to upgrade to 5.x I believe you have to work with pixel units. If you are interested in the interactive way perhaps look at my ui table handler in the forum. |
Which node are you reporting an issue on?
table node from node-red-node-ui-table
What are the steps to reproduce?
Not sure how exactly to reproduce. I am using several simple tables with 2 columns. First Align left, 75%, second align right 25%
All are configured with the same settings
What happens?
The column width is displayed incorrectly at random. I have seen this with two separate NR instances, in Firefox, MS Edge and on iPhone and Android (Firefox). Sometimes they are displayed correctly, most of the time at least one or two are displayed incorrectly
What do you expect to happen?
Tables should have the size configured in node config
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: