While it's nice to be able to see the chrome preview change as I make edits in Brackets, the tradeoff of inconsistent behavior (often the preview just stops working), a second instance of chrome running, and the inability to use the chrome inspector make this feature useless.
Instead, Brackets should build live preview like Browsersync or Livereload do it, refreshing the browser when the page is loaded, and using a standard, local url to preview the page.
@dmaweb Thanks for using Brackets and sharing your concern regarding live preview feature. Inconsistent behavior is definitely a niggling issue which we are looking at. The whole point of live preview is to leverage on live preview of the page which is being edited. In fact we are getting in a reverse inspect feature in next release to highlight a corresponding element in editor. However I am in complete agreement with you that web inspector is a Savior for a web developer. We are also thinking in the same line where we could leverage the power of blink inspector. Rest assured all future releases of Brackets is going to make a web developers effort more streamlined.
Most helpful comment
@dmaweb Thanks for using Brackets and sharing your concern regarding live preview feature. Inconsistent behavior is definitely a niggling issue which we are looking at. The whole point of live preview is to leverage on live preview of the page which is being edited. In fact we are getting in a reverse inspect feature in next release to highlight a corresponding element in editor. However I am in complete agreement with you that web inspector is a Savior for a web developer. We are also thinking in the same line where we could leverage the power of blink inspector. Rest assured all future releases of Brackets is going to make a web developers effort more streamlined.