RC test: Molarity 1.3.0-rc.1

[pixelzoom]

RC version:
http://www.colorado.edu/physics/phet/dev/html/molarity/1.3.0-rc.1/molarity_en.html

iFrame test:
http://www.colorado.edu/physics/phet/dev/html/molarity/1.3.0-rc.1/molarity_en-iframe.html

Text matrix:
https://docs.google.com/spreadsheets/d/1tb4vFUYbqCPPIDPOiV6BkamOZiZyWujxaF4al_2q4k4/edit#gid=288440115

In addition to the test matrix, please perform these specific tests on 1 or 2 platforms:

• stringTest=double (double all strings)
• stringTest=long (excessively long strings)
• stringTest=X (short strings)
• stringTest=rtl (right-to-left text direction)
• stringTest=xss (test for security issues, passes if it does NOT redirect to another page)
• full screen test
• screenshot test

The previous test was 1.3.0-phetiodev.3, see phetsims/tasks#865. There are no issues to verify from that test, and this RC version uses the same shas.

Please mention this issue in any GitHub issues that you create.

[jonathanolson]

It looks like this RC is using SHAs that don't include all of the necessary patches for phetsims/scenery-phet#312, specifically it references phetsims/scenery-phet@db4bf96 in the dependencies.json, which is missing the fix phetsims/scenery-phet@727d5bd.

@pixelzoom, can this be cherry-picked to a "molarity-1.3" branch in scenery-phet, and then have an RC with that fix included?

@phet-steele can you screen other RCs to make sure that they include that commit?

Also, can someone check to see if the following email was received (I sent it out, but saw no replies):

@ariel-phet, can we come up with a better process than phet-dev emails (if my email sent correctly?)

[pixelzoom]

@phet-steele please stop all testing, we're starting over.

@ariel-phet fyi.

[pixelzoom]

@jonathanolson handled cherry-picking the fix to a new molarity-1.3 branch of scenery-phet, while I observed. So I should now be able to proceed with creating 1.3.0-rc.2.

[pixelzoom]

Testing continues with 1.3.0-rc.2 in #13.

Closing.