-
Notifications
You must be signed in to change notification settings - Fork 8
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
Spot checks for delayed chipper startup #354
Comments
@KatieWoe I think this would be good to basically test on all supported platforms and in the ways @jonathanolson mentions above. High priority for the moment since not much in the testing queue, but will get bumped down if other things come up. |
Additionally, the above HTML is now at the link https://phet-dev.colorado.edu/olsonjb/hidden-test.html, so I'd like that tested on all platforms if possible. |
Testing Platforms
@KatieWoe, please review. |
@jonathanolson the hidden/unhidden html doesn't seem to load (nothing on the progress bar) on Win 10 firefox. |
Sim looks fine on the hidden/unhidden page of iOS 12 safari. But the page can be scrolled up and down. |
https://phet-dev.colorado.edu/olsonjb/hidden-test.html not working on Win7 + IE. |
Safari 10.1.2 on Mac 10.10.5 won't show the sim when the hidden button is clicked much like in Edge.
|
QA is done. Let me know if the comments above should be issues and where they should go. |
Thanks! |
See phetsims/chipper#764 and phetsims/tasks#1002 for background information.
I've dev-deployed https://phet-dev.colorado.edu/html/charges-and-fields/1.1.0-dev.7 with the patch for those issues, which will delay the sim require.js startup until suitable conditions (i.e. iframe that isn't hidden) exist.
Some example HTML (can be saved as a file and viewed in a browser) that can help trigger the issue is:
I'd recommend trying out the phet and phet-io brand files in multiple configurations (LoL, anywhere iframes are concerned, and particularly any place the sim may be hidden) to see if this breaks anything.
I'd also appreciate some cross-browser testing to ensure that this won't break on any of our supported platforms.
@ariel-phet, anything else you think should be tested for this change?
The text was updated successfully, but these errors were encountered: