everweij
commented
3 years ago Hi @natew, I'm so sorry for my late response. I remember reading your issue many weeks ago, but totally forgot to leave a message. Anyway, the last couple of weeks I've worked on v2.0.0 of this lib, and today I finally released it. There are definitely some great ideas you got there. In v2, the layers aren't eagerly calculated anymore, and instead wait untill the layer is actually open/shown. I think this will boost the performance in your case a lot. I'm looking forward to experiment with the ResizeObserver / IntersectionObserver stuff. I'll put this on the roadmap for now, but hopefully I have some time left to investigate this somewhere in the upcoming weeks.
In general it would be a huge win to have the library defer to ResizeObserver + IntersectionObserver where possible.
We have a big results list where each item has 3 popovers. So 3 * 25 in the typical case. I’m noticing in multiple cases react-laag is calling getBoundingClientRect during mount/unmount. This is totally unnecessary.
One, it can call that once you hover no need to do it eagerly. Second, it can do it only when it’s intersecting on the screen. Third, it can use ResizeObserver to avoid some calls altogether.
This is sorely needed for React. There just doesn’t exist a great Popover primitive and that sucks. I should help write it instead of bitching here, but instead I’ll just bitch for now. I spent way too much time writing one a while ago but it didn’t have the elegance of API as you have here.
Would be absolutely awesome to see movement here.
Even better: make a generic utility for tracking size that combines the best of MutationObserver (can it help avoid some work?) ResizeObserver, IntersectionObserver and finally when all else fails getBoundingClientRect. I’d love to have a micro library that made a sane API for that to use elsewhere.