I'm not seeing any change? I took this line > <big>Dubious Domain<br> And changed it to > <big>Dubious Domain219<br> in SeaMonkey 2.19 & saved the page as html. And changed it to > <big>Dubious Domain220<br> in SeaMonkey 2.20 & saved the page as html. Comparing the two pages, the only difference is /219/220/.
Opened page in current trunk version, changed a couple of letters, saved it, observed differences: 1) » and — in original file became > and - respectively, so problem is currently fixed 2) Some minor attributes rearrangements in td tag, nothing critical, setting close date to somewhere close to 2.23 release
All of the problems don't show up by just loading the file from the local drive and saving it again using the Composer. It is only after making certain changes and saving it that one gets a save that alters the main file and creates several support files that are definitely not desired. I am attaching the corrupted file and the support files in the subdirectory dub-dom-bad_files with files donatre.html and show_ads.js. In that directory is a subdirectory donate_data with the file blue-small.gif
The intended use is to download an HTML file from the remote site using ftp or a method of saving that does not alter links or create support files, because the intent is to edit it and ftp it back up to the remote server for viewing, not viewing from the local drive except in the composer window. That means support files will only appear if their links are absolute rather than relative, although those should work. The main desire is that the adsense ads not be altered, but continue to work before and after editing other parts of the page and saving the result to be ftp'd up to the server again.
Check this build - http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/seamonkey-2.23a1.en-US.linux-i686.tar.bz2 and see if problem is present there
Tried http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/seamonkey-2.23a1.en-US.linux-i686.tar.bz2 and the problem remains, both for altering external links and for the special characters.
Some target release needs to be tested on a file containing EVERY HTML character code. That should be standard QA procedure.
Resolved per whiteboard