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
First of all, thank you so much for saving me some work!!! Always super appreciated.
I'm curious if there's plans to handle resizing with a hostlistener or maybe a service to fire off a width recalc on a debounce to keep parent and fixed portion widths congruent? Currently am working around this by throwing the container to scrolltop = 0 but that's klunky and won't correct resize issues until resize end. So what we see is the fixed header stay its pre-resize width after resize and would really love to keep this as an npm since I wouldn't be able to PR any improvements back anyway but can imagine others would appreciate it also.
Thanks for taking the time though regardless!
The text was updated successfully, but these errors were encountered:
First of all, thank you so much for saving me some work!!! Always super appreciated.
I'm curious if there's plans to handle resizing with a hostlistener or maybe a service to fire off a width recalc on a debounce to keep parent and fixed portion widths congruent? Currently am working around this by throwing the container to scrolltop = 0 but that's klunky and won't correct resize issues until resize end. So what we see is the
fixed
header stay its pre-resize width after resize and would really love to keep this as an npm since I wouldn't be able to PR any improvements back anyway but can imagine others would appreciate it also.Thanks for taking the time though regardless!
The text was updated successfully, but these errors were encountered: