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
Describe the bug
In the list of Strava segments for an activity, there are ΔKOM and ΔPR columns which do not populate. They just have spinning wheels that last forever, instead of showing e.g. how far behind the KOM or PR I was.
To Reproduce
Steps to reproduce the behavior:
Go to any Strava activity containing at least one segment.
Scroll down to the list of segments.
Look at the data in the ΔKOM and ΔPR columns.
Expected behavior
The ΔKOM and ΔPR columns should probably tell how far behind the KOM or PR my effort was.
Screenshots
Outdoor ride:
Virtual/Zwift ride:
Environment
OS: Windows 11 Home
Browser name and version: Chrome 130.0.6723.117
Web extension version: 7.2.1
Additional context
I have not managed to find anything about these columns in the documentation, FAQ or previously logged issues.
I also have Sauce for Strava installed, so I was not 100% sure if these columns were from Elevate or Sauce. However, the developer of Sauce said he had not seen those columns, so I suppose they are from Elevate :)
The text was updated successfully, but these errors were encountered:
Describe the bug
In the list of Strava segments for an activity, there are ΔKOM and ΔPR columns which do not populate. They just have spinning wheels that last forever, instead of showing e.g. how far behind the KOM or PR I was.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The ΔKOM and ΔPR columns should probably tell how far behind the KOM or PR my effort was.
Screenshots
Outdoor ride:
Virtual/Zwift ride:
Environment
Additional context
I have not managed to find anything about these columns in the documentation, FAQ or previously logged issues.
I also have Sauce for Strava installed, so I was not 100% sure if these columns were from Elevate or Sauce. However, the developer of Sauce said he had not seen those columns, so I suppose they are from Elevate :)
The text was updated successfully, but these errors were encountered: