diff --git a/docs/manual/en/introduction/How-to-run-things-locally.html b/docs/manual/en/introduction/How-to-run-things-locally.html index b55b880ab3845c..d7ad74baf6b488 100644 --- a/docs/manual/en/introduction/How-to-run-things-locally.html +++ b/docs/manual/en/introduction/How-to-run-things-locally.html @@ -122,64 +122,6 @@
- Enable the develop menu using the preferences panel, under Advanced -> "Show develop menu - in menu bar". -
- -- Then from the safari "Develop" menu, select "Disable local file restrictions", it is also - worth noting safari has some odd behaviour with caches, so it is advisable to use the - "Disable caches" option in the same menu; if you are editing & debugging using safari. -
-Close all running Chrome instances first. The important word here is 'all'.
- -- On Windows, you may check for Chrome instances using the Windows Task Manager. - Alternatively, if you see a Chrome icon in the system tray, then you may open its context - menu and click 'Exit'. This should close all Chrome instances. -
- -Then start the Chrome executable with a command line flag:
- -chrome --allow-file-access-from-files
-
- - On Windows, the easiest is probably to create a special shortcut icon which has - added the flag given above (right-click on shortcut -> properties -> target). -
- -On Mac OSX, you can do this with
- -open /Applications/Google\ Chrome.app --args --allow-file-access-from-files
- about:config
- security.fileuri.strict_origin_policy
parameter
- Other simple alternatives are [link:http://stackoverflow.com/q/12905426/24874 discussed here] on Stack Overflow.