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

Masses briefly stop moving when switching between vertical and horizontal normal modes #84

Open
Nancy-Salpepi opened this issue Nov 9, 2021 · 1 comment

Comments

@Nancy-Salpepi
Copy link

Test device
iPad Air 2

Operating System
15.1

Browser
Safari

Problem description
phetsims/qa#733

I've only seen this on the iPad thus far: The masses will briefly stop moving when switching between horizontal and vertical amplitudes on the Two Dimensions Screen.

Steps to reproduce

  1. On the Two Dimensions Screen, increase the Number of Masses to 100
  2. Grab a Mass from the middle and move it to one of the edges. Release.
  3. Switch back and forth between Vertical and Horizontal radio buttons.

Visuals

particles.temporarily.freeze.mov
Troubleshooting information: !!!!! DO NOT EDIT !!!!! Name: ‪Normal Modes‬ URL: https://phet-dev.colorado.edu/html/normal-modes/1.0.0-rc.1/phet/normal-modes_all_phet.html Version: 1.0.0-rc.1 2021-11-03 19:33:33 UTC Features missing: applicationcache, applicationcache, touch Flags: pixelRatioScaling User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36 Language: en-US Window: 1313x633 Pixel Ratio: 2/1 WebGL: WebGL 1.0 (OpenGL ES 2.0 Chromium) GLSL: WebGL GLSL ES 1.0 (OpenGL ES GLSL ES 1.0 Chromium) Vendor: WebKit (WebKit WebGL) Vertex: attribs: 16 varying: 31 uniform: 1024 Texture: size: 16384 imageUnits: 16 (vertex: 16, combined: 80) Max viewport: 16384x16384 OES_texture_float: true Dependencies JSON: {}
@Nancy-Salpepi Nancy-Salpepi added the type:bug Something isn't working label Nov 9, 2021
@pixelzoom
Copy link
Contributor

pixelzoom commented Nov 9, 2021

This is not something that will be addressed for the prototype. I'll label it as deferred, so that it can be evaluated for the final public version.

Also not a bug - there is nothing incorrect about the behavior. So I'm removing the "bug" label and adding "performance" label.

@pixelzoom pixelzoom removed their assignment Nov 9, 2021
@pixelzoom pixelzoom added priority:5-deferred type:performance and removed type:bug Something isn't working labels Nov 9, 2021
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