Skip to content
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

Not all changesets shown in history view on low zoom levels #3423

Open
kallejre opened this issue Jan 15, 2022 · 0 comments · May be fixed by #5473
Open

Not all changesets shown in history view on low zoom levels #3423

kallejre opened this issue Jan 15, 2022 · 0 comments · May be fixed by #5473
Labels
bug Something is broken or not working as expected changesets Related to the Changesets feature ui User Interface

Comments

@kallejre
Copy link

URL

https://www.openstreetmap.org/history#map=1/0/0

How to reproduce the issue?

To reproduce issue:

  1. Got to OSM website
  2. From the menu in top-left corner, select "History" (Ajalugu in attached screenshot)
  3. Zoom out or adjust width of browser window until all continents are visible at least twice
  4. (Optional): To make effects of the bug more clear, make sure that longitude of both edges of the map are approximately same

Issue: Only changesets from that very narrow gap are shown.
Expected behaviour: All changesets around the world are shown.

Screenshot(s) or anything else?

The bug is caused by Leaflet's method .wrap() on line 62 of history.js. The easiest fix is to simply remove said method because it's used for offsetting user's bbox of current viewport into valid latitude/longitude. However, function that processes the passed parameter in changesets_controller.rb as of now uses simple number comparison to filter changesets and don't mind unusual bbox parameters. Bit more sophisticated fix is to add client-side bbox validation where too large bboxes would be clipped from -180/180 meridian. But bigger question is that since this issue was introduced as single commit 8 years ago and not fixed since, is this a bug or an intentional feature to reduce server load?

I came across this bug while working on PR #3417 and had actually already fixed it there using the lazy method, but wanted to clarify if wrapping was intentional or it was added by accident.

Screenshot with sample of the issue (loaded bit more changesets than the default 20 to show the trend). Note the map boundaries.

pilt

@tuckerrc tuckerrc added bug Something is broken or not working as expected changesets Related to the Changesets feature ui User Interface labels Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken or not working as expected changesets Related to the Changesets feature ui User Interface
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants