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

Pixelratio autodetection broken on chrome on osx #819

Open
alexanderkyte opened this issue Feb 19, 2014 · 1 comment
Open

Pixelratio autodetection broken on chrome on osx #819

alexanderkyte opened this issue Feb 19, 2014 · 1 comment
Labels

Comments

@alexanderkyte
Copy link

After having a number of very strange event issues, I tracked down the issue. The hitCanvas on all of my layers were being drawn with a pixelratio of less than one, but my canvas was being drawn at full pixels. While it is true that I'm currently scaling the screen out a little, to maybe 0.75 of the eventual rendering size, the library gives behavior that is not desired. Essentially all items drawn within the canvas but outside of the slightly smaller hitCanvas are unable to be clicked. This can be seen on the latest stable chrome on OSX.

The issue lies in that the browser will scale down the area of the hitCanvas along with the layer in question. I think the pixelratio logic on webkit-based browsers should be a no-op.

@lavrton lavrton added the bug label Mar 9, 2014
@toomuchpete
Copy link

This is, I think, the same issue:

In both Chrome, Firefox, and Safari on OSX 10.8.5, KineticJS v5.1.0 sets the pixelRatio to 1 instead of 2, even though window.devicePixelRatio is 2. Manually setting the pixel ratio on the canvas sharpens up rendering

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

No branches or pull requests

3 participants