Open abgowda opened 4 years ago
Scenario 2: Same behavior is encountered if a port is blocked and trying to launch Brackets with remote debugging enabled with the blocked port.
Steps:
Block port 1234 by executing the below command: (sudo pfctl -sr 2>/dev/null; echo "block drop quick on lo0 proto tcp from any to any port = 1234") | sudo pfctl -e -f - 2>/dev/null
Launch Brackets with remote debugging enabled on port 1234.
Expected behavior : Brackets shouldn't notify that remote debugging is enabled for the blocked port.
Actual behavior: Brackets launches with incorrect info bar displayed.
Note: http://localhost:1234 does not load the content in the browser
1.Launch Brackets 1.14.1 from the terminal/Cmd line with the port number.
Expected: Brackets shouldn't launch with the remote debugging enabled for the same port number for which the Brackets was launched first.
Actual behavior: Brackets launches with the debugging enabled for the same port number and incorrect info bar displayed.
Brackets 1.14.1-17752 Platforms: Win /Mac /Ubuntu
@yprasad1 @narayani28 @jha-g