Fix ui problems
What does this MR do?
Fixes some user interface problems.
How confident are you it won't break things if deployed?
confident
Screenshots (if applicable)
Description | Before | After |
---|---|---|
Cleaner spacing | ![]() |
![]() |
Store buttons | ![]() |
![]() |
Clear container boundaries for store page | ![]() |
![]() |
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
set a "for:" label to indicate who will be affected by this change -
set the "API change" label if changes in the API are not backward compatible -
added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label) -
added an entry to CHANGELOG.md
-
added a short text in the release notes to /release-notes/YYYY-MM.md -
Once your MR has been merged, you are responsible to create a testing issue in the Beta Testing forum: https://foodsharing.de/region?bid=734&sub=forum. Please change the MRs label to "state:Beta testing". - Consider writing a detailed description in German.
- Describe in a few sentences, what should be tested from a user perspective.
- Also mention different settings (e.g. different browsers, roles, ...) how this change can be tested.
- Be aware, that also non technical people should understand.
Edited by Anton Ballmaier
Merge request reports
Activity
assigned to @AntonBallmaier
added 2 commits
added 34 commits
-
189118c6...ebc0877e - 33 commits from branch
master
- c5fd7344 - Merge remote-tracking branch 'origin/master' into fix-ui-problems
-
189118c6...ebc0877e - 33 commits from branch
changed milestone to %Release "Mandarine
"added Frontend / Design forFS Community labels
marked the checklist item added to the next milestone (see https://gitlab.com/foodsharing-dev/foodsharing/-/milestones, unless it has a "for:Dev" label) as completed
Please register or sign in to reply