Seamonkey 1.1.18 (and earlier) progressively mess up a web page I am trying
to let a nontechnical user edit, as each time they use Seamonkey to edit the
page more <br> tags get inserted.

The page has a CSS based popup menu, with source that looks like this when I
'view source' in a browser other than Seamonkey:

<ul class="nav">
        <li class="menunosub"><a href="/index.html">Home</a></li>
        <li class="menu"><a href="#">About Us</a>
                <ul class="menu">
                <li><a href="/PhotosVideos.html">Photos and Videos</a></li>
                <li><a href="/history.html">History</a></li>
                <li><a href="/News.html">News</a></li>
                <li><a href="/BOD/ALL.html">Board and Staff</a></li>

The same page loaded into Seamonkey (via Open Web Location in a Composer
window) and viewed looks like:

<ul class="nav">

<li class="menunosub"><a href="/index.html">Home</a></li>

<li class="menu"><a href="#">About Us</a>

<ul class="menu">

<li><a href="/PhotosVideos.html">Photos and Videos</a><br>

</li>

<li><a href="/history.html">History</a><br>

</li>

<li><a href="/News.html">News</a><br>

</li>

<li><a href="/BOD/ALL.html">Board and Staff</a><br>

</li>
Note the introduction of gratuitous <br> tags in each *nested* <li> element
(but not in the outer <li>s). After editing, these <br> tags are saved back
to the web page, and on the next edit, yet another set of <br> tags is
introduced. The empty space in the pulldown menus grows with every edit.

If the source is simply viewed in the Seamonkey browser, it's just like all
the other browsers (no extra <br> tags), but the Composer reliably
introduces them.

I Googled, then searched the archives to this list after joining, but no
luck. So maybe nobody knows a workaround?

The page I reference can be viewed at <http://www.dunngardens.org/>.
-- 
Mike Casteel
Seattle, WA
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to