When using alpine-morph, if an element begins polling and then changes its poll interval, the existing poll interval is retained, and a new, additional interval is created.
Each time the interval is changed, the browser sends bigger and bigger waves of requests.
If the hx-trigger is removed entirely, all previously-established poll intervals continue. I'm not sure whether this is intentional.
To reproduce, start with this HTML, then make several changes to the every Ns while keeping an eye on the DevTools network tab
When using alpine-morph, if an element begins polling and then changes its poll interval, the existing poll interval is retained, and a new, additional interval is created.
Each time the interval is changed, the browser sends bigger and bigger waves of requests.
If the
hx-trigger
is removed entirely, all previously-established poll intervals continue. I'm not sure whether this is intentional.To reproduce, start with this HTML, then make several changes to the
every Ns
while keeping an eye on the DevTools network tab