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

canvas tiling in chrome 18.0.1025.142 + #118

Open
olamothe opened this issue Mar 30, 2012 · 2 comments
Open

canvas tiling in chrome 18.0.1025.142 + #118

olamothe opened this issue Mar 30, 2012 · 2 comments

Comments

@olamothe
Copy link

There seems to be a problem with newer version of chrome that breaks the tiling of canvas inside polymaps, like in this example :

http://polymaps.org/ex/mandelbrot.html#1.00/0/0

When you first load the example, you can see that the translate attributes doesn't seem to be applied correctly to each canvas.

I tried with the newest available version of Chrome (dev channel) , and it looks like loading the example just crash the browser.

Any ideas ?

@olamothe
Copy link
Author

olamothe commented Apr 2, 2012

There seems to be a problem when you change the default value of tileSize from 256 to something else : eg. tileSize of 512 seems to break the tiling of the canvas in newer version of chrome.

@olamothe
Copy link
Author

The same error occur with the newest version of Safari, on Lion. The underlying problem it seems is the hardware accelerated canvas. If you start either browser with the option off the problem disappear :

For chrome : start from the command line with the flag --disable-accelerated-2d-canvas

For safari on MacOs activate the debug menu from the terminal :
defaults write com.apple.Safari IncludeDebugMenu 1
defaults write com.apple.Safari IncludeInternalDebugMenu 1
Uncheck the 'Enable canvas accelerated drawing'

With the hardware acceleration disabled, the problem disappear. I reported the bug on the webkit bugzilla : https://bugs.webkit.org/show_bug.cgi?id=83189

In the meantime, I don't know if any of you guys had any ideas for a way to fix this with some hack inside polymaps

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

1 participant