I have pages created with the other versions of HTML Editor.

When I use to correct them I would switch between the code editor and visual editor and it would tell me it had to save the page so I would and there was no issues.

Now when I switch between the code and visual editors and save the page it goofs up my webpage.

For some reason it takes some of the top portion of my page and copies it to the bottom of my page.

**It also does this weird thing where it scans down thru the whole code.

What is up with that?

I guess I see from reading a above post that they use different coding for both so that is why things get messed up.

Why did they have to change it?

The HTML Editor is two tools in one package to be used as a visual editor or a text editor. A pop-up informs you that changes to the code may result prior to switching from text mode to visual mode.

Is this changed in just this version?

Can I get the older version?

I like switching back and forth between the code and visual tabs. I like using Visual tab for font changes and such.

Have a read here
http://www.coffeecup.com/forums/html-editor/html-editor-do-not-use-both-code-tab-and-visual-tab-read-this/

It hasn't changed in a very long time, it's been this way for many many versions.

The older version did not change the code to the point of copying blocks of code. I only experienced this with 2010. I am having the same problem and somehow it needs to get resolved or I will have to switch to a new software.

Have you tried running the code cleaner or processing your page through HTML Tidy? Typically when the Visual Editor has these sorts of problems it is because there is a lot of invalid markup on the page and the editor does not know what to do. It can only make so many assumptions on how to process the page and if there are too many problems, it will go into panic mode.

Try running the page through http://infohound.net/tidy/ and then save the new page and try using the Visual Editor again.

I have been having the same problem as Mark, and it also started after upgrading to 2010.

I'll try the suggestion from Scott

-Chris

using windows 7 x64

I am having this problem too. How did you get it resolved??? It only started with the 2010 update.