Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

Confusing live preview workflow when used with files outside of the current project #5975

Open
jasonsanjose opened this issue Nov 13, 2013 · 1 comment

Comments

@jasonsanjose
Copy link
Member

  1. Open any project
  2. File > Open... and choose an HTML file that is not in the current project's tree
  3. Start Live Preview
  4. Observe file: URL
  5. Try live HTML editing - Fail
  6. Open or drag in a CSS file that's associated with the HTML file
  7. Try CSS selector highlighting and Live CSS editing - Pass

A user might incorrectly expect live HTML editing to work in this case.

It might be better if we nag the user somehow (maybe a status bar message or some other notification) whenever certain live preview features are disabled.

@redmunds
Copy link
Contributor

redmunds commented Dec 9, 2013

What about adding text to the initial Live Preview modal informational (i.e. "we'll only show you this once") dialog that says something like:

"Live HTML (and any other features?) only work for files in current Brackets project and when using the Brackets built in server."

Note 1: We never really explain what a "Brackets project" is
Note 2: The "Brackets built in server" probably needs more explanation

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants