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

Firefox line-arc graphics acceleration path incorrect #214

Open
jonathanolson opened this issue Apr 11, 2014 · 6 comments
Open

Firefox line-arc graphics acceleration path incorrect #214

jonathanolson opened this issue Apr 11, 2014 · 6 comments

Comments

@jonathanolson
Copy link
Contributor

See phetsims/acid-base-solutions#104

@jonathanolson jonathanolson self-assigned this Apr 11, 2014
jonathanolson added a commit to phetsims/acid-base-solutions that referenced this issue Apr 11, 2014
@jonathanolson
Copy link
Contributor Author

Planning to do per-path workarounds for now, I'm hoping Firefox fixes the bug before I would need to add a Scenery/Kite-level workaround.

@jonathanolson
Copy link
Contributor Author

Not fixed in Firefox Aurora 32.0a2 (2014-06-16), we'll want to submit a report about this.

@jonathanolson jonathanolson changed the title Potential Firefox graphics acceleration path problem Firefox line-arc graphics acceleration path incorrect Oct 13, 2014
@jonathanolson
Copy link
Contributor Author

Acid Base Solutions example bad arrow:

M 0.00000000000000000000 0.00000000000000000000 L 25.00000000000000000000 0.00000000000000000000 L 25.00000000000000000000 0.00001000000000000000 L 25.00000000000000000000 0.00000000000000000000 A 18.00000000000000000000 18.00000000000000000000 0 0 1 14.41986545873548486441 -3.43769410125094587727 M 25.00000000000000000000 0.00000000000000000000 A 18.00000000000000000000 18.00000000000000000000 0 0 0 14.41986545873548486441 3.43769410125094587727

@pixelzoom
Copy link
Contributor

@jonathanolson

Acid Base Solutions example bad arrow:

Please elaborate. Is this something that needs to be fixed in ABS?

@jonathanolson
Copy link
Contributor Author

No, it's the path without the workaround in place to help with debugging the Faraday's Law issue.

@jonathanolson
Copy link
Contributor Author

Test case wasn't easily present. Here's one that I'll test when on Windows:

var svg = document.createElementNS( scenery.svgns, 'svg' )
var path = document.createElementNS( scenery.svgns, 'path' );
svg.appendChild( path )
path.setAttribute( 'd', 'M 0.00000000000000000000 0.00000000000000000000 L 25.00000000000000000000 0.00000000000000000000 L 25.00000000000000000000 0.00001000000000000000 L 25.00000000000000000000 0.00000000000000000000 A 18.00000000000000000000 18.00000000000000000000 0 0 1 14.41986545873548486441 -3.43769410125094587727 M 25.00000000000000000000 0.00000000000000000000 A 18.00000000000000000000 18.00000000000000000000 0 0 0 14.41986545873548486441 3.43769410125094587727' )
document.body.appendChild( svg )
svg.setAttribute( 'width', 640 );
svg.setAttribute( 'height', 320 );
path.setAttribute( 'transform', 'matrix( 3, 0, 0, 3, 100, 100 )' )
path.setAttribute( 'style', 'fill: none; stroke: black;' )

@jonathanolson jonathanolson removed their assignment Sep 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants