Skip to content

Fix *all* OS / browser-dependent scattergl text oddities #2780

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
etpinard opened this issue Jul 5, 2018 · 4 comments
Closed

Fix *all* OS / browser-dependent scattergl text oddities #2780

etpinard opened this issue Jul 5, 2018 · 4 comments
Labels
bug something broken

Comments

@etpinard
Copy link
Contributor

etpinard commented Jul 5, 2018

Follow-up of #2737

scattergl text works well on @dy's Windows laptop in both Chrome, FF and IE11 (please correct me if I'm wrong @dy), but features a few oddities in FF on MacOS and Ubuntu 16.04 and Safari.

Copying @alexcjohnson 's report:

On Mac OS 10.13.5, retina display. For reference here's the SVG text_chart_arrays mock, which AFAICT looks identical on Chrome, FF, and Safari:
chrome svg
But the gl2d version looks bold and blurry (perhaps this is retina-only, related to #2756?), and there are first-load issues in FF (missing some items entirely) and Safari (wrong font).
Here's Chrome:
chrome gl
FF the first render in a given tab is missing some items:
ff gl first
But the second gets them all:
ff gl second
And Safari on first render has the wrong font for "Text G":
safari gl
but it's fixed on second render:
safari gl second

@etpinard etpinard added the bug something broken label Jul 5, 2018
@etpinard
Copy link
Contributor Author

bug report from @chriddyp

The latest scattergl text is not rendering for me on Firefox 61.0, MacOS 10.13.4. It renders for me in Chrome.

Chrome:
image

Firefox:
image

Firefox Console:
image

@etpinard
Copy link
Contributor Author

assigning @dy

@chriddyp
Copy link
Member

@gvwilson
Copy link
Contributor

Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson

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