Elements tab of the Debug tool window.
Live Edit works through the JetBrains Chrome extension and therefore is available only in Google Chrome.
Installing the JetBrains Chrome Extension
To install the JetBrains Chrome extension
- Open the JetBrains IDE Support page in Chrome Web Store.
- Click the Add to Chrome button , and then click Add in the Confirm New Extension dialog box that opens. The Add to Chrome button changes to Added to Chrome .
Activating Live Edit
- In the Settings/Preferences dialog (Ctrl+Alt+S), click Debugger under Build, Execution, Deployment, and then click Live Edit. The Live Edit page opens.
- Select the Update application in Chrome checkbox. This enables on-the-fly preview of HTML and CSS.
- Set the elapsed time for applying the changes to a running application: accept the default value
300 msor specify a custom value using the spin box next to the corresponding field.
- To configure highlighting, select the Highlight current element in browser on caret change checkbox. Otherwise, during a debugging session, you will have to hold Shift and click the element to highlight.
- To have WebStorm restart the server if automatic upload of changes to the client-side code fails, select the Restart if hotswap fails checkbox. See
Activating, de-activating, and uninstalling JetBrains Chrome extension
Control over the JetBrains Chrome extension is provided through the chrome://extensions page:
- To open the page, just type
chrome://extensionsin the Chrome address bar.
Alternatively click Customize and control Google Chrome (), choose Settings on the context menu, and then click Extensions on the chrome://settings page that opens.
- To deactivate the extension, clear the Enabled checkbox. The checkbox name changes to Enable.
- To activate the extension, select the Enable checkbox.
- To uninstall the extension, click the Remove from Chrome button .
Changing the default port for connecting to WebStorm
During a debugging session with Live Edit, the Chrome extension listens to the port of the JetBrains IDE from which the extension was invoked. Each IDE including WebStorm has its own default port on which it starts.
If for some reason the default WebStorm port is already busy, WebStorm finds the closest available port and starts on it. This results in a conflict: WebStorm is running on a "new" port while the Chrome extension still listens to the port of a previously started product.
The conflict reveals when you initiate a debugging session with Live Edit: the extension fails to connect through the default port, WebStorm waits for connection from the extension and displays the following message with the port number where it is actually running (for example,
current port 63342):
To fix the problem, specify the actual WebStorm port in the Chrome extension options
- Right-click and choose Options on the context menu. A web page with the Chrome extension options opens showing the parameters to connect to WebStorm.
- In the IDE Connection area, specify the actual WebStorm port in the Port spin box.
Overriding the default CORS settings
Suppose the page you are debugging with Live Edit requests a resource which is, for security reasons, protected against access through CORS settings. You can enable access to the protected resources by changing the Chrome extension options.
To override the default CORS settings
- Right-click and choose Options on the context menu. A web page with Chrome extension options opens showing the parameters to connect to WebStorm.
- In the Force CORS text box, type the pattern that defines the URL addresses you want to make accessible, for example: