Hi

First of all I don't know whether or not the HTML Editor is supposed to work like this, but if it does then I find it quite cumbersome to use !

My problem is that when I write a piece of code and thereafter would like to view its impact on a page then I have to save first !

Well, I don't have a problem with that except that there is a "Preview" tab - now I wonder why it is there and what its purpose is ?

Isn't the purpose of the preview tab to let a user have a quick look at the changes without saving ?

Also, I wonder wheter or not htere is a few keyboard shortcut for switching betwen the Code Editor tab and the Preview tab ? - I would really love to be able to use:

F5: for Preview tab

F6: for Code Editor tab

Hi Viking. Are you sure your preview doesn't work without saving. Mine does. What happens when you click on the preview tab? As far as keyboard short cuts for tab switching I don't know that there are any. Maybe someone else will be able to find them.

Hi Eric

After reading your post I get a bit nervous that I hadn't paid enough attention when switching between the view tabs, however, I have just tried a few times more and I can say with a 100% certainty that changes in the code is not updated when i switch to the Preview tab !

I have also tried to see if the a piece of text would change from normal to italic when I use the splitscreen, but I only see the change once I have saved.

Ups ! - I think I have forgotten to mention that I have two files opened at the same time:

default.htm

style.css

My problem is that the changes I make into the .css doesn't update in the css preview when I click on the Preview tab.

But changes in the html code in the .htm is getting updated immediately, but not the code from the css-file (until I save the css file).

Hi Viking
If you make changes to default.htm you can preview the changes without saving.
If you make changes to style,css you have to save style.css before you see the effect in default.htm

If your working with a CSS style sheet then you'll have to save that in order make the changes show on the HTML page in the preview tab just as Dave says. Sorry for the confusion.

Yes, that is correct and it also works for me.

However, from my experience you'll have to have to make a save whenever you wish to preview changes in the style.css using the splitscreen (F12)

HTML Editor is seeming only able to auto-update files which has a browser executable file-extension like .htm, html etc.

Well, I'll guess that I will just have to accept this fact and do a lot of saving, but it does making changes to a .css file really cumbersome.

Well, I have a more serious problem with the internal preview, whether I have saved my page or not.

I always use HTML 5 and CSS3 these days, and it seems like the compatibility with the newest browsers does not exist yet in the internal preview.

When I look at a page using the Coffeecup preview, everything looks out of place, while it works like it should in all the browsers I use for testing (Firefox 5 as my default browser, IE 9, Opera (latest version) and Google chrome (latest version too).).

I looked through the support pages and saw something in the Preferences setting, which I do not seem to have, although I use the latest version of the HTML Editor: a dropdown menu which lists the possible versions of Internet Explorer (although, as far as I am aware, I have only IE 9 on my hard disk).
However, the internal preview is not doing its job like it should.
Am I missing something, or, if not, can the Coffeecup team do something about that, please, as it is a lot quicker, when you have to have a quick peek at the preview of your page, to use the internal preview, rather than to wait for the external browser to load.

I have attached a picture of how it looks in the internal preview in the HTML Editor, and one of how it should (and does) look in Firefox 5.

Frankie, I guess you didn't see my post from last week.

http://www.coffeecup.com/forums/html-ed … d-testers/

I think this update will give you the functionality you need.

Also, Frankie, if you could post the url to your site, we could take a look at your code and see if there is something in there that makes the differences in the view.