-
Notifications
You must be signed in to change notification settings - Fork 7
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
There is no way to access the next collection if one clicks the X instead of Next Collection button after completing a collection #124
Comments
This is a side effect of using common code It looks like I shouldn't be using Dialog to support this behavior. A sim-specific panel will need to be implemented. |
… of Dialog. Is created upon collection completion and disposed when next collection is triggered. #124
The above changes should now match the behavior of the Java version. I'll release a dev version to compare. Edit: Matching the java version means, that when the panel is present the user can still interact with other sim elements. It shouldn't have been implemented as a dialog. Can you confirm in this dev version @KatieWoe? |
Underlying problem does seem solved in the dev version. |
The legacy version of this sim allows for the interaction of the sim while the next collection box is present. If we wanted to go ahead with removing this behavior that would be a decision for designers. Thoughts @arouinfar? |
@Denz1994 I think you should take a look at phetsims/balancing-chemical-equations#137. The game in BCE uses a sim-specific dialog-like thing that isn't actually a dialog. For a11y, a dialog would be preferable, but converting the sim to use a dialog is non-trivial. It seems really weird to me to allow user to interact with the sim while the dialog-like-thing is open. In addition to the behavior shown in #124 (comment), I'm able to open the 3D dialogs or reset the collection (so the sim contradicts the dialog message) which feels pretty buggy to me. I think the simplest UX would be to use |
@arouinfar @Denz1994 after chewing a bit...what about this idea...
Something like this... |
@Denz1994 @arouinfar I agree we should probably go with the balancing chemical equations approach and stop items in the sim from being pickable when the dialog appears. I do not think having a close button move to the next collection would be a good UX. It seems we could still allow the close button and use the dialog approach. The close button could just close the dialog |
…ctionality has been moved to the MoleculeCollectingScreenView. #124
A few changes that should be reviewed in this dev version:
Note: The URL for the dev version includes an |
@Denz1994 almost...two tweaks.
|
This has been implemented so this behavior also occurs if the user clicks outside of the dialog to escape the prompt, not just if they hit the close button. The above tweaks have been implemented in https://phet-dev.colorado.edu/html/build-a-molecule/0.0.0-dev.39/phet/build-a-molecule_all_phet.html. @ariel-phet should review when possible. |
@Denz1994 behavior is all correct now. I might have a polish or two, but we will deal with that in a main polishing issue. Closing. |
Test device
Windows 10 Laptop
Operating System
Windows 10
Browser
Chrome
Problem description
For phetsims/qa#459
When one completes a collection they are presented with a text box which has two options, Next Collection and an X button in the corner. Clicking the X will close the text box and prevent the user from accessing the next collection at all, even after a reset and the completion of the collection a second time.
Steps to reproduce
Visuals
Troubleshooting information:
!!!!! DO NOT EDIT !!!!!
Name: Build a Molecule
URL: https://phet-dev.colorado.edu/html/build-a-molecule/0.0.0-dev.23/phet/build-a-molecule_all_phet.html
Version: 0.0.0-dev.23 2019-11-20 23:29:39 UTC
Features missing: generatedcontent, touch
Flags: pixelRatioScaling
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36
Language: en-US
Window: 1536x754
Pixel Ratio: 1.25/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: 4095
Texture: size: 16384 imageUnits: 16 (vertex: 16, combined: 32)
Max viewport: 32767x32767
OES_texture_float: true
Dependencies JSON: {}
The text was updated successfully, but these errors were encountered: