Bug description

[up-poll] uses the configured interval (or the default of 10 seconds) for the first wait. After that, it effectively uses a timeout of 0, meaning that a new request starts one browser tick after the old request has finished.

This only occurs if the server skips rendering by returning an X-Up-Target: :none header. Otherwise, the old fragment would be replaced and the next wait interval would be the "first" wait again.

Therefore, I was not able to write a reproduction project.

Expected behavior

The specified interval is honored for every wait, not just for the first.

Additional context

The bug seems to be in radio.js:115

and line 123

Because of Line 115, doSchedule is called with the return value of the up.reload call for the first argument, which is an object. This object is then fed into setTimeout, which silently defaults to a delay of 0.