Custom Query (49 matches)

After setting up staging (#47) I've tested the current version in my mobile device (motorola motog 4 play, android 7, latest firefox) and I found several details that need fixing:

• Login background does not have proper size/width in mobile phones in vertical position:

• The workout details in the workouts list in both the dashboard and the profile page are messed up in narrower resolutions (see the | separator for cycling | distance | time, etc):

If you look at the same pages in a horizontally oriented device, it looks ok:

• Viewing the dashboard on mobile phone shows workouts first, stats afterwards, while on the profile page it shows the stats and chart first, then the list of workouts. IMHO it makes more sense to show the chart/stats first, as the list of workouts can be quite long

​

Basically we serve the same image the user provided us with, everywhere. We do some scaling, but only at css/styles level, which means that the full-sized image has to be loaded even on devices with small screens.

We need to implement some code to serve the image in different sizes, then pick up the proper size when we are rendering those profile pictures.

Basically, some times it seems chrome takes the screenshot before the map is fully loaded, which ends in maps like this:

Which are totally useless.

We need a way to reliable generate those maps.

(hint: maybe look into how to make chrome wait for the map to be loaded?)