Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

blank/partial map #4600

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments
Closed

blank/partial map #4600

openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: porjo
[Submitted to the original trac issue database at 12.44pm, Sunday, 30th September 2012]

If I search for 'maugham court' on the Nominatim page, I get 2 results displayed in the left-hand panel:

  • Maugham Court, Sacramento, California, 95632, United States of America
  • Maugham Court, Lower Island, Whitstable, Canterbury, Kent, South East England, England, CT5 1DA, United Kingdom

If I click on the second result from the left-hand panel the map areas goes blank in Firefox (15.0.1). In Internet Explorer 9 I see a strip of the map on the left of the map area and the rest of the map area is blank. (I haven't tested any other browser)

If I search for 'maughum court whitstable' the map area shows a complete map i.e. no error

@openstreetmap-trac
Copy link
Author

Author: porjo
[Added to the original trac issue at 12.34pm, Monday, 1st October 2012]

I've tested this on Linux using Firefox 15 with the same result (original test was on Windows 7)

I've just discovered that if I resize the browser window, this causes the map area that was previously blank to display the correct map...so perhaps a CSS/JS bug?

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 12.49pm, Monday, 1st October 2012]

I can reproduce that with Firefox and Opera (chromium works fine) and the same thing also happens on the main OSM site. So I suspect there is a bug somewhere in OpenLayers. But why exactly for 'Maugham Court' and only for 'Maugham Court' leaves me completely confused. It might help to find a second case where the bug appears.

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 12.52pm, Monday, 1st October 2012]

Yes I looked at this last night on the main site and I'm pretty sure it's an OpenLayers bug. My best guess is that it relates to this code:

https://github.com/openlayers/openlayers/blob/master/lib/OpenLayers/Layer/Grid.js#L469

which as you can see from the comment is supposed to force a retile when you warp from one side of the world to another.

What you will see if you look at a failed case is that the tiles are positioned at massively crazy offsets in the back buffer - hundreds of thousands of percent and things. Zooming out or changing window size will cause a retile and fix it.

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 9.35pm, Monday, 1st October 2012]

I can see the offsets but can't really make sense of the code. I've extracted the example and filed a bug against OpenLayers. Follow-ups should go there: openlayers/openlayers#696

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant