Skip to content

Mozilla plot point size on scattergl plots is not equal as in Chrome and as in SVG plots #1287

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

Closed
ifll opened this issue Jan 9, 2017 · 15 comments
Labels
bug something broken
Milestone

Comments

@ifll
Copy link

ifll commented Jan 9, 2017

I have been doing some trials on my own about scatter and scattergl 2D plots. This is what I found:

SVG plot:

  • Mozilla performs good and exactly the same as Chrome when inputing a list of sizes for the points being displayed. Length(Points) == Length(List of sizes)

  • Chrome performs good an exactly the same as Mozilla in SVG when inputing a list of sizes for the points being displayed. Length(Points) == Length(List of sizes)

WebGL plot:

  • Mozilla performs good but different as Chrome in WebGL and SVG and different as Mozilla in SVG as well.

  • Chrome performs good and same as Chrome in SVG and Mozilla in SVG but different as Mozilla in WebGL

To summarize, at some point the rendering of the scattergl plot in mozilla oversizes the points even if you input a specific point size. Chrome in SVG and WebGL perform the same

Would that be a bug? Would this be solved?

Thank you very much!!

@etpinard
Copy link
Contributor

etpinard commented Jan 9, 2017

Can you share a reproducible example?

@ifll
Copy link
Author

ifll commented Jan 9, 2017

Check out the point size differences between chrome and mozilla running this two codepends in both browsers:

scatter: https://codepen.io/anon/pen/pRjLwL
scattergl: https://codepen.io/anon/pen/dNYmVP

FYI I was using those browsers on UBUNTU 16.04

Chrome: 55.0.2883.87
Mozilla: 50.1.0

@ifll
Copy link
Author

ifll commented Jan 9, 2017

In chrome there is a very small difference on point size, but in mozilla there is a huge one with webGL...

@ifll
Copy link
Author

ifll commented Jan 9, 2017

Between SVG implementations there is no difference between browsers. So Chrome in WebGL perfomes almost exactly as in SVG, but Mozilla changes a lot... Too much for the app I am doing... and I can't force the useres to use chrome....

@etpinard etpinard added the bug something broken label Jan 10, 2017
@etpinard
Copy link
Contributor

Thanks for the report

cc @dfcreative

@etpinard etpinard added this to the On-par gl2d milestone Jan 10, 2017
@ifll
Copy link
Author

ifll commented Jan 10, 2017

Any idea when this could be solved?

@rreusser
Copy link
Contributor

FWIW I can't confirm that I'm seeing this. For the scattergl plot in mozilla 50.1.0 in OS X 10.11.4, I see:

screen shot 2017-01-10 at 11 09 05

So there may be a component of OS or hardware dependency involved.

@etpinard
Copy link
Contributor

Thanks for checking @rreusser !

@ifll
Copy link
Author

ifll commented Jan 10, 2017

Mozilla 50.1.0 Ubuntu 16.04 SVG plot

captura de pantalla de 2017-01-10 17-20-27

Mozilla 50.1.0 Ubuntu 16.04 WebGL plot

captura de pantalla de 2017-01-10 17-20-42

@etpinard
Copy link
Contributor

@ifll yes, I can confirm the behavior in Ubuntu 16.04

@ifll
Copy link
Author

ifll commented Jan 10, 2017

It seems to be Ubuntu Specific, as I have checked in windows and it worked...

@dy
Copy link
Contributor

dy commented Apr 7, 2017

We use monospace default system font for rendering symbols, it is likely that mozilla has whether different monospace font or uses different rendering approach.
@ifll can you show screenshots of chrome/mozilla webgl plot?

@ifll
Copy link
Author

ifll commented Apr 10, 2017

Currently I cannot dedicate some time on it, I need to face other stuff. Maybe during the week or on the next week I can find some time and try to provide them. Sorry for this and hope it is not an inconvinience....

@dy
Copy link
Contributor

dy commented Jan 15, 2018

1e300c4 adds sizes test

@etpinard
Copy link
Contributor

done in #2258

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

No branches or pull requests

4 participants