Per the meeting minutes below:

1. The dom tree contents will be split out of the Navigator and put into a separate window.  The Navigator will revert to its normal behavior of showing the current static file structure.  Synchronization between the Navigator and the source is as it is today.

2. The dom tree ONLY appears when we have something running with nb integration, and disappears when the connection is broken.

3. The dom tree synchronizes ONLY with selection of a node in the browser, or via direct selection by the user. 
  - While the dom tree is open, selecting in any HTML, JavaScript, CSS -- 
    or any file from any project -- will have no impact on it. 
  - The dom tree window will continue to offer a go to source feature 
    to let users synchronize a source destination with it (if possible).
  - We explored the idea of offering a feature in an HTML file to locate 
    the current node in the dom tree, but don't have any specific plans 
    to pursue.  Might be a nice ER for later consideration.

4. The CSS styles window synchronizes ONLY with the dom tree.  It appears and disappears with the dom tree.  That means we will no longer have an empty CSS Styles window open prompting the user to run something.  You only get the CSS Styles window when you have the dom tree window, which you only get if you're running with NB integration in a supported target.

5. The CSS styles window should change to reinforce that it's following the dom tree node selection, and not a file (it currently suggests its synchronizing to a file).  For example:  <div id=windowResizer> - CSS Styles.  To avoid clutter, I would show an id if there is one, otherwise just the tag.  You'll get the styling details in the window.

6. The dom tree window title should be changed to reinforce the connection to the browser session.  Since we have a "Browser Log" window, how about if we call this "Browser DOM"  I don't think we need the word "tree."  We don't say "Navigator Tree" :-)

7. The dom tree window should have a panel added at the top that includes a 16 x 16 version of the target device/browser icon and the url of the current running file.  The URL can truncate if needed.

8. Currently, the CSS Styles window does double-duty:  it lets you style the current selected dom node when something is running, and it lets you style a css file normally in "document" mode.   This is an open design point given these decisions:  to avoid confusion, we may need to split these into 2 separate windows:  1 for the dom-related dynamic editing, and one for static css file editing.