After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 765947 - Map should not allow you to go beyond top and bottom boundaries
Map should not allow you to go beyond top and bottom boundaries
Product: gnome-maps
Classification: Applications
Component: map view
Other All
: Normal enhancement
: ---
Assigned To: gnome-maps-maint
Depends on:
Reported: 2016-05-03 16:57 UTC by Inactive account
Modified: 2018-03-26 13:50 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement

Maps_Ubuntu_Top_Bad_Design.png (181.18 KB, image/png)
2016-05-03 17:06 UTC, Inactive account
Maps_Ubuntu_Bottom_Bad_Design.png (226.25 KB, image/png)
2016-05-03 17:06 UTC, Inactive account

Description Inactive account 2016-05-03 16:57:48 UTC
The map currently allows you to go beyond the top and the bottom boundaries but this looks rather ugly so I think that it should be made so that you can't go beyond either of them. Otherwise you just get this rather ugly look:

- Maps_Ubuntu_Top_Bad_Design.png
- Maps_Ubuntu_Bottom_Bad_Design.png

I am running Ubuntu GNOME 15.10 with GNOME 3.18 but the issue is also present on Ubuntu GNOME 16.04 with GNOME 3.20. The same issue exists for the left and the right sides, however I believe that this [1] would be a better fix for that issue.

I initially reported this issue here but thought I should also do so upstream:
Comment 1 Inactive account 2016-05-03 16:59:11 UTC
Comment 2 Inactive account 2016-05-03 17:06:21 UTC
Created attachment 327245 [details]
Comment 3 Inactive account 2016-05-03 17:06:46 UTC
Created attachment 327246 [details]
Comment 4 GNOME Infrastructure Team 2018-03-26 13:50:36 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: