Topic: Homepage mobile testing
kaputtnik Topic Opener |
Posted at: 2025-01-24, 09:30
Hello everybody, the website wasn't adapted to be used on mobile phones phones in the past. I spent a lot of time to change this and want to ask if anyone with a mobile phone or tablet can test the changes. Some things are still not like it should be on mobile phones, but a start is done. The main change for now is to make the basic site work on mobile phones at all and to have a solution for all the information we provide on the main site, like the menu on the top (beside the logo), the latest posts box and the main menu. Some sub pages, like Maps or screenshots are not adapted right now. Forum topics may need also some love but in general this is working. So if you have a mobile phone or a tablet please test the current changes on https://alpha.widelands.org and give some feedback here in this topic. Thanks in advance! Top Quote |
hessenfarmer |
Posted at: 2025-01-24, 22:29
I am not sure whether I remember things correctly, but it seems mobile access has defintily improved. all GUI elements are reachable except the upper right items. Profile, messages, scheduler and logout should be single logo based buttons rather then classical textbased hyperlinks. Top Quote |
kaputtnik Topic Opener |
Posted at: 2025-01-25, 10:23
If you load the current page https://www.widelands.org on a smartphone you always have to zoom in and scroll the page around to reach certain links. At least this was my experience with the old layout.
Probably each in a row f it's own? I'll take a look. Top Quote |
kaputtnik Topic Opener |
Posted at: Yesterday 15:18
Using image buttons needs too much height, imho. I've reworked the login part for small devices, putting each link in a separate line and give a bit more space around them. Please take a look again. For me this is fine now. Top Quote |
hessenfarmer |
Posted at: Yesterday 16:35
this is not deployed yet I believe Top Quote |
kaputtnik Topic Opener |
Posted at: Yesterday 18:02
You probably need to reload, or clean the cache. But it seems this solution does not work for some mobile phone browsers, e.g. chrome or firefox have problems with this. So further testing is not needed until a better solution is found… Thanks anyway Edited: Yesterday 18:02
Top Quote |