-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Route labels taking too much space on mobile #132
Comments
Hi. Is anybody on this issue now? Willing to try and make my first open-source contribution |
Hi @viorelrj, don't think anyone started to work on this. You can take it. Thanks! 🚀 |
@iamandrewluca, upd: sorry, will actually have to pass this one. |
No problems. 🙂 |
@viorelrj, could you provide some more context? It would help us if we knew the rationale behind your decision, so we could adapt. If the task is not clearly defined - we can make refine the description. Alternatively, if you just don't have the time - it is out of our control, but at least we know this is not because of obvious deficiencies in our requirements. And just in case - if you're not confident you can implement this, we're here to provide mentoring. You can get guidance from top-notch engineers like Andrei, or from less bright [but still supportive] people like me. |
@roata , thanks for great reply! The reason is that it is only now that I noticed that this project might slightly be a subject of non-concurrency contract I signed at my current job, thus will have to stop the initiative. Thanks for understanding and offering to help. |
The introduction of #128 brought a minor inconvenience for mobile users - roughly 25% of the screen is now occupied by the list of selected routes.
This can be resolved by adding a "collapse" button that might look like this:
It will compress this widget into a more compact representation, which can be expanded back into its normal state:
This functionality can be retained for the regular, desktop version too. In other words, this doesn't have to be a "mobile only" feature.
The text was updated successfully, but these errors were encountered: