- Why cross-domain debugging:
Take embedded web developers that the code is run on the board, I have an elegant front-end developer to complete each change to the code are packaged on the board, the board opened with an address, which is the human thing to do? ? ?
- How cross-domain debugging:
1. Upgrade to the latest version of Chrome
Chrome shortcut on the Right desktop, select "Create Shortcut", rename ChromeDebug, of course, named for the flowers you will do next sector
3. Right-new shortcut, select "Properties" to open the property dialog box
4. Add the following parameters after the target start-up: - user-data-dir = "c: \ ChromeDebug" --test-type --disable-web-security, ( each - in front of a space ) of " OK "button to save the settings
5. Start parameters --user-data-dir = "c: \ ChromeDebug", Chrome will represent the c: \ ChromeDebug access the user data, the newly opened window ChromeDebug is a new non-polluting Chrome, no bookmarks, history, extensions, etc., need to re-install extension
6. Now as long as the front-end code written request addresses to absolute addresses can be directly debugging friends