Stop telling users how to disable security #15334
Conversation
It is arguably irresponsibly to tell users to disable their securtiy to do development. Especially when the alternatives are safe and easy, taking 30 seconds to 2 minutes max
|
Note there is still a reference to changing security settings under the Personally, I agree that permanently changing a setting in the browser is probably a bad thing for us to recommend. Starting the browser from the CLI in a mode that allows local file access bothers me much less, but if Chrome is the only browser that supports that I'm OK with pulling the section rather than recommending only a single browser. |
|
Thanks! |
Stop telling users how to disable security. mrdoob#15334
|
It seems to me that this page should explain why it no longer tells about any in-browser command-line options, especially since, especially for Windows users, installing Ruby or Python when they're not used for any other purpose, or setting up a local HTTP server, may be seen as extra hoops to jump through to enable local testing of three.js applications (compared to in-browser command line options). (To be clear, I have no complaints about these extra hoops, but others might.) |
|
Another option for Windows users is to install this: https://chrome.google.com/webstore/detail/web-server-for-chrome/ofhbbkphhbklhfoeikjpcbhemlocgigb but I think Google was going to deprecate Chrome Apps |
These are hoops that anyone who is serious about web development will have to jump through at some point, so they're not unreasonable. For people who are just starting to experiment, using something like codesandbox.io is probably a better route. |
Current wording offers two options and suggests we'll explain both, but then only explains the second. As discussed in #15334 we should not encourage users to change their browser's security settings.
* Recommend a local server, don't present it as second option Current wording offers two options and suggests we'll explain both, but then only explains the second. As discussed in #15334 we should not encourage users to change their browser's security settings. * Clean up
* Recommend a local server, don't present it as second option Current wording offers two options and suggests we'll explain both, but then only explains the second. As discussed in mrdoob#15334 we should not encourage users to change their browser's security settings. * Clean up
6 participants
It seems kind of irresponsible to tell users to disable their security to do development. Especially when the alternatives are safe and easy, taking 30 seconds to 2 minutes to setup.