Moving things over to using HTML tables is proving tricky, as to get draggable resizing to play nicely, there will be a few tweaks needed to apply to the structure of the grid - shifting some parts from the header and body into the grid proper. This link goes into one of the pitfalls that can happen with Angular components and HTML grids: https://medium.com/javascript-everyday/when-to-use-an-attribute-selector-for-angular-components-7e788ba1bfe7
I'm unsure if dragged size changes would be savable, but I believe the switch to HTML tables will be worth it - an added benefit would be easing the ability to add screenreader support.
The link Ruth provided is very useful, with a caveat - the eg Grid is designed to be reliant on divs, rather than using HTML tables. I have a WIP branch here that's beginning to implement draggability in the grid, and shifts the grid over to tables: /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ khuckins/ lp1778311- web-column- on-the- fly-resizing
https:/
Moving things over to using HTML tables is proving tricky, as to get draggable resizing to play nicely, there will be a few tweaks needed to apply to the structure of the grid - shifting some parts from the header and body into the grid proper. This link goes into one of the pitfalls that can happen with Angular components and HTML grids: https:/ /medium. com/javascript- everyday/ when-to- use-an- attribute- selector- for-angular- components- 7e788ba1bfe7
I'm unsure if dragged size changes would be savable, but I believe the switch to HTML tables will be worth it - an added benefit would be easing the ability to add screenreader support.