-
Notifications
You must be signed in to change notification settings - Fork 2
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
Document supported browsers in an open source manner #1042
Comments
@ariel-phet will create a document that lists the browsers we support in phet-info. |
@zepumph the more I think about this, why don't we link to the example testing matrix? I believe I brought that up, but for some reason people maybe didn't think it was a good idea That is really the ground truth document. Whenever we add or remove a platform, that is where we do it. Having a separate document just seems like a maintenance burden where things are likely to get out of sync. if you can convince me there is value in a second document we can revisit, but if not, lets just link that example test matrix in the necessary places. |
I think that the important piece is to make sure that the whole world has read access to it. I'm not sure that is set up at this time. |
Document here: https://github.com/phetsims/phet-info/blob/master/doc/supported-browsers.md Closing |
Related to #1037 and phetsims/query-string-machine#39 (comment) and #1018. It feels like we should have a place where devs can see what browsers we support.
Over in phetsims/query-string-machine#39 (comment), @samreid mentioned that likely https://phet.colorado.edu/en/help-center/running-sims is the best place for end-users, but there isn't a central location where we let it be known to devs that the phet code base (including underlying and potentially independent libraries like QSM and scenery) doesn't support certain browsers. I am running into this quite a bit as we drop support for IE, and it think it would be a good step for the project to take in terms of transparency and open-source philosophy.
My recommendation (expanding on @samreid's in that link) is to put this somewhere in top level documentation, and link to that where ever needed.
Some proposals:
supported-browsers.md
, link to it inphet-development-overview.md
, and in any library README file needed. This modular doc could be easily updated by QA et. all as we rotate out what is tested, and could be a clear ground truth.phet-development-overview.md
.What do people think? Marking for dev meeting
The text was updated successfully, but these errors were encountered: