phetsims / number-play

"Number Play" is an educational simulation in HTML5, by PhET Interactive Simulations.
GNU General Public License v3.0
3 stars 1 forks source link

Unintentional overlap of objects #180

Closed KatieWoe closed 2 years ago

KatieWoe commented 2 years ago

Test device Dell Operating System Win 11 Browser Chrome Problem description For https://github.com/phetsims/qa/issues/822 It is possible to get non-card objects to fully overlap with each other fairly easily. If you overlap two in a corner, then overlap a third, the movements trying to prevent overlap will cause overlap with another object. This may not be worth addressing, but I wanted to document it just in case. Steps to reproduce

  1. Go to a screen and scene with non-card objects
  2. Put one object in the corner of the play area
  3. Take a second object and overlap it with the first (the second should move slightly)
  4. Take a third object and overlap it with the first (it will jump to overlap the second)

Visuals overlaps

Troubleshooting information:

!!!!! DO NOT EDIT !!!!! Name: ‪Number Play‬ URL: https://phet-dev.colorado.edu/html/number-play/1.1.0-dev.1/phet/number-play_all_phet.html Version: 1.1.0-dev.1 2022-07-28 23:33:39 UTC Features missing: applicationcache, applicationcache, touch Flags: pixelRatioScaling User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Language: en-US Window: 1280x649 Pixel Ratio: 1.5/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: 30 uniform: 4096 Texture: size: 16384 imageUnits: 16 (vertex: 16, combined: 32) Max viewport: 32767x32767 OES_texture_float: true Dependencies JSON: {}
Nancy-Salpepi commented 2 years ago

This happens on the Ten and Twenty screens as well

https://user-images.githubusercontent.com/87318828/181916061-ce093971-721f-4121-9132-95d87e66fa22.mp4

amanda-phet commented 2 years ago

I would say it's a known issue. We've discussed it in the context of the Lab screen, and it is something I am ok with leaving as-is.

chrisklus commented 2 years ago

@amanda-phet and I confirmed this as a won't-fix and decided to close, thanks all.