New log type ascent does not finish loading on idle tab

[killakalle]

I'm not a 100% sure about the steps to reproduce, but that's my best guess.

To reproduce

1. Open a crag with a route list
2. Get sidetracked and do something else for 15(?) minutes
3. Remember the still open theCrag tab and return
4. Select a few routes and click "New log ascent"
5. Wait for log ascent screen to finish loading (it never finishes)
6. Click cancel
7. ....still loading...

Expected

• [ ] Can log ascents regardless of how long tab has been idle

[lordyavin]

I experience never ending loading too. A refresh F5 of the page resolves it but that should not be necessary.

[killakalle]

This happened to me while using the new tick interface on mobile. It got stuck on loading (always showing the name of the first route) and I clicked Save several times to see if it would react.

Apparently in the background it was switching to the next route in the queue but not updating the FE. You can tell that the FE was somehow stuck because the same ascent comment was saved for each route.

[scd]

This has been addressed

[killakalle]

@scd I still encounter this problem.

Form does not finish loading - eventually, a reload button appears.

After clicking the reload button, the only thing I notice is that the button disappears. However, the form does not load

[scd]

I have fixed the control and transparency around loading. If you press reload does it work?

Fixing our sites scaling issues is way more complex.

[killakalle]

If you press reload does it work?

No. After clicking the reload button, the only thing I notice is that the Reload button disappears. However, the form does not load.

[scd]

I just went through the procedure to test this and it worked for me. Can you confirm if you can do the same thing.

1. Go to the page where you are logging an ascent
2. Disconnect from the Internet
3. Log the ascent and wait for the Reload button.
4. Connect to the Internet
5. Press Reload

First I want to see if there is something about your set up that is systemically not working.

[killakalle]

@scd I can follow the steps above and log an ascent successfully. However, this scenario is also different from when I encounter the problem.

I encounter the problem when I keep a route page open for a longer time and come back to it to log an ascent.

e.g. you are at a crag climb a route and log it. Then you leave the page open on your phone while climbing the next route, then come back to the already open route page and try to log the next route.