No extensions installed. Every troubleshoot & semi-maybe related reported issue studied extensively. (maybe some didn't show, as I would look at one and later try to find it again and it would be gone.)
(Nice troubleshoot doc btw)
online research to enabling chrome remote debug results in microsoft software suggestion and android debugging through chrome, so my problem may be that I have not figured out how to enable remote debugging
live preview experimental feature: multi-browsing ON does not affect problem, does not change to default browser
Description
Live Preview opens chrome (initially chromium, then I installed chrome in an attempt to fix the problem)
Chrome tab is labeled "waiting" but displays nothing
Brackets reports error, says to enable remote debugging
Steps to Reproduce
Using 'gettting started' file index.html OR 'my own folder' imadethisfile.html (i made it in eclipse, if that matters)
click on side-ways lightning bolt
What happened:
chrome(and previously chromium) opens new window (even when a window is already open)
(even with multi-browser feature on and default set to firefox, chrome is what opens)
Brackets reports error
Expected behavior: to see my html file appear so I can watch changes to code
Versions
Brackets release 1.9 experimental build 1.9.0-17312 (release 189f6d39a) downloaded from brackets.io big blue button
Chrome version 59.0.3071.109 (Official Build) (64-bit)
Linux Mint version 17.3
Notes:
this is not the first time I have run Brackets. An issue explained the topmost error in the picture as a one-time run. This happens every time. It does not seem to affect anything, but I have also not attempted to add any extensions.
the 2 groups of 'failed to load resource' are from attempting to open the 'getting started' file twice. the 'get' errors are all from a single attempt to open my own file on this run of brackets.
please break it down for any suggestions. I have only been on linux for a week (windows 7/8/10 user) and have enough trouble with 'apt-get install'. Things need to be explained to me more than would usually be required.
Prerequisites
No extensions installed. Every troubleshoot & semi-maybe related reported issue studied extensively. (maybe some didn't show, as I would look at one and later try to find it again and it would be gone.) (Nice troubleshoot doc btw)
online research to enabling chrome remote debug results in microsoft software suggestion and android debugging through chrome, so my problem may be that I have not figured out how to enable remote debugging
live preview experimental feature: multi-browsing ON does not affect problem, does not change to default browser
Description
Live Preview opens chrome (initially chromium, then I installed chrome in an attempt to fix the problem) Chrome tab is labeled "waiting" but displays nothing Brackets reports error, says to enable remote debugging
Steps to Reproduce
Using 'gettting started' file index.html OR 'my own folder' imadethisfile.html (i made it in eclipse, if that matters) click on side-ways lightning bolt What happened: chrome(and previously chromium) opens new window (even when a window is already open) (even with multi-browser feature on and default set to firefox, chrome is what opens) Brackets reports error
Expected behavior: to see my html file appear so I can watch changes to code
Versions
Brackets release 1.9 experimental build 1.9.0-17312 (release 189f6d39a) downloaded from brackets.io big blue button Chrome version 59.0.3071.109 (Official Build) (64-bit) Linux Mint version 17.3
Notes: this is not the first time I have run Brackets. An issue explained the topmost error in the picture as a one-time run. This happens every time. It does not seem to affect anything, but I have also not attempted to add any extensions.
the 2 groups of 'failed to load resource' are from attempting to open the 'getting started' file twice. the 'get' errors are all from a single attempt to open my own file on this run of brackets.
please break it down for any suggestions. I have only been on linux for a week (windows 7/8/10 user) and have enough trouble with 'apt-get install'. Things need to be explained to me more than would usually be required.