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

openlayers 2.13.1 tile update problem in chrome #1207

Open
sertan0134 opened this issue Dec 17, 2013 · 14 comments
Open

openlayers 2.13.1 tile update problem in chrome #1207

sertan0134 opened this issue Dec 17, 2013 · 14 comments

Comments

@sertan0134
Copy link

Hi,
I just added a sample code to http://jsfiddle.net/Sertan/YkqL9/19/

My problem is that if you pan on the map and afterwards click "gotextent button" which calls zoomtoextent method, the map is zoomed to extent of the polygon however some part of the polygon in the previous tile still remains there which should not be there anymore. This problem does not occur on open layer version 2.12 or in firefox with version 2.13.1.

screen example can be seen below.

zoomtoextent

@kevbradwick
Copy link

We use OL to build our own mapping library and we've also found this issue with the recent 2.13.1 upgrade. After some testing, it appears to be isolated to SVG rendering in newer webkit/blink engines. The table below illustrates affected browsers that we have tested;

Browser Affected
IE10 No
IE9 No
Firefox (26 OSX) No
Opera (12.16) No
Safari (6.1) Yes
Safari (5.1) No
Chrome (32 OSX) Yes
Chrome Canary (34 OSX) Yes

@ahocevar
Copy link
Member

ahocevar commented Feb 3, 2014

Initial investigation shows that this only happens with Google base layers.

@kevbradwick
Copy link

Quick update, we've found that if you turn on GPU acceleration for svg elements the problem goes away.

svg {
    -webkit-transform: translateZ(0);
}

@sertan0134
Copy link
Author

thank you for your effort chrome 32.0.1700.102 m version this problem does not occur.

@darrenlucas
Copy link

The problem does occur. Screenshot of issue in Chome 32.0.1700.102:
tile_update_problem

@sertan0134
Copy link
Author

interesting does not occur my computer

@bartvde
Copy link
Member

bartvde commented Feb 3, 2014

what OS are you guys on? I've heard reports of some issues only on Chrome on Windows, not on OSX

@kevbradwick
Copy link

@bartvde For me it's on OSX (Lion and Mavericks). We're pretty sure it has something to do with Google's Maps GPU acceleration.

Problem goes away with;

.olForeignContainer svg {
    -webkit-transform: translateZ(0);
}

@ahocevar
Copy link
Member

ahocevar commented Feb 4, 2014

@kevbradwick Would you be able to create a pull request with this css snippet?

@ahocevar ahocevar reopened this Feb 4, 2014
@kevbradwick
Copy link

@ahocevar sure, shall I add to the examples a page that demonstrates the problem?

@bartvde
Copy link
Member

bartvde commented Feb 4, 2014

I think it would be more suitable to have a manual test case instead of an example https://github.com/openlayers/openlayers/tree/master/tests/manual

@kevbradwick
Copy link

@bartvde cool, no problem, I'll create one this morning

@mprins
Copy link
Contributor

mprins commented Feb 4, 2014

FWIW I tested on:

  • Chrome 34.0.1821.0 canary
  • Chrome 32.0.1700.107 m
  • Opera 19.0.1326.59
  • Opera Next 19.0.1326.45
  • Opera Developer 20.0.1387.16

on winXP and could not reproduce in any of those.
However it still seems a good idea to try and trick-force GPU acceleration for svg elements, though it seems that chrome has been doing this for some time

inspecting chrome://gpu/ or opera:gpu may be useful

@kwadrat
Copy link

kwadrat commented Mar 13, 2014

@kevbradwick I observe similar problem on:
http://ivan.sanchezortega.es/chrome_ol_bug/
using MS Windows 7, Google Chrome 33.0.1750.149 m
After adding 10 layers the tiles don't get refreshed. Disabling GPU support by commenting-out lines:
-webkit-transform: translateZ(0);
-webkit-backface-visibility: hidden;
fixes problem.

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

No branches or pull requests

7 participants