Skip to content
This repository has been archived by the owner on Apr 3, 2022. It is now read-only.

Render bug in google-chrome-stable on linux #118

Open
ghost opened this issue Mar 18, 2015 · 3 comments
Open

Render bug in google-chrome-stable on linux #118

ghost opened this issue Mar 18, 2015 · 3 comments
Labels

Comments

@ghost
Copy link

ghost commented Mar 18, 2015

  • Disclaimer, I believe this is a bug in the browser or with esri leaflet, not necessarily with geobin, as opening the geobin in other browsers does work.

URL:
http://geobin.io/xCPZsm0y5k

When I have the page open and post to the url:
correct_geobin

When I open the same bin in a second window or tab:
new_tab_geobin

Seems like the esri maps just get hung up in some intermediate render step, as the screen does momentarily look just like this in other browsers before cleaning itself up.

@ghost ghost added the question label Mar 18, 2015
@ungoldman
Copy link
Member

@CourtF that's esri-leaflet so the rendering engine is leaflet. unless the call to the tile server is hanging it may be a leaflet issue.

@ghost
Copy link
Author

ghost commented Mar 18, 2015

Some guys at the office were seeing this in Firefox on OSX as well, but then it worked with a reload. Probably a leaflet issue as you say.

@ungoldman
Copy link
Member

It may also be angular's page rendering interfering with leaflet's rendering. I was doing some weird stuff to reload references to basemaps to circumvent an issue like this early on.

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

No branches or pull requests

1 participant