07-19-2021, 06:35 PM
Hello everyone,
I just create a pull request that takes the TableLayoutWdg and converts it to use <div> elements instead <table>
This has been a long time coming. Using the <table> elements has been a nightmare and caused all sorts of weird sizing issues.
However, the change is pretty drastic as it converts all <table>, <tr>, <td> tags to <div> elements. The classes and structure are the same so if you happened to have any code that search elements using class names, then everything should still work fine. If they specifically looked for the table elements, then you may need to update the code.
I have not merged the pull request in the hopes that some of you could try it out first since it's a pretty big change.. Most of it working quite well, however, I have seen some instances where if you reorder columns, resize and then press refresh, it can mess up a bit. A quick resize on one of the columns fixes the issue. I will look into that sometime, but I think the table behaves way better and more predictably now.
Let me know if there are any big issues that would prevent this from being merged into the main branch.
I just create a pull request that takes the TableLayoutWdg and converts it to use <div> elements instead <table>
This has been a long time coming. Using the <table> elements has been a nightmare and caused all sorts of weird sizing issues.
However, the change is pretty drastic as it converts all <table>, <tr>, <td> tags to <div> elements. The classes and structure are the same so if you happened to have any code that search elements using class names, then everything should still work fine. If they specifically looked for the table elements, then you may need to update the code.
I have not merged the pull request in the hopes that some of you could try it out first since it's a pretty big change.. Most of it working quite well, however, I have seen some instances where if you reorder columns, resize and then press refresh, it can mess up a bit. A quick resize on one of the columns fixes the issue. I will look into that sometime, but I think the table behaves way better and more predictably now.
Let me know if there are any big issues that would prevent this from being merged into the main branch.