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

Specifying CSS transforms as a renderer option (cssTransform) for a higher-level node causes sub-nodes to be cut off #142

Closed
jbphet opened this issue Oct 9, 2013 · 2 comments
Assignees
Labels

Comments

@jbphet
Copy link
Contributor

jbphet commented Oct 9, 2013

When CSS transforms are turned on for a higher-level node, there seem to be cases where sub-nodes get cut off. This is currently being seen in the RewardNode class in Build an Atom. The problem occurs when the call to the supertype looks like this:

Node.call( this, { renderer: 'svg', rendererOptions: { cssTransform: true }, pickable: false } );

...and goes away when it looks like this:

Node.call( this, { renderer: 'svg', pickable: false } );

I am attaching two screen shots that correspond to the two lines above. On the first, you can see how nodes are cut off part way down.

baa-reward-with-css-transforms

baa-reward-no-css-transforms

@samreid
Copy link
Member

samreid commented Oct 9, 2013

I saw a similar problem when trying to apply CSS to a layer of moving sub-objects in Forces and Motion: Basics screen 2.

@jonathanolson
Copy link
Contributor

This was very Scenery 0.1-specific, should not happen now.

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