Closed Bug 386699 Opened 18 years ago Closed 13 years ago

Empty font style tags are easily left behind

Categories

(SeaMonkey :: Composer, defect)

Product:
SeaMonkey
Component:
Composer
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 When using the composer to edit text and using the font style buttons in the normal view, often empty font style tags are left behind when deleting text later. Reproducible: Always Steps to Reproduce: 1. write a few lines of text 2. select one of them with the mouse and assign a font style (e.g. bold) 3. go on with other work 4. select the bolded line with the mouse and delete it (press delete twice to also delete the empty line) Actual Results: An empty font style element (span style="font-weight: bold;") is left behind. It can be backspaced out when you position the cursor correctly but it is not visible in normal view, only in html view. It clutters the html text with more and more unnecessary tags as the text is being edited. Expected Results: Probably it would be better to delete a style element once it becomes empty. This would be a recursive or repeating operation, as more than one style element can be nested (e.g. big and bold). Not specific to Seamonkey, has been present in Mozilla for a long time.
duplicate of bug 145881 ?
Yes it looks like bug 145881 describes other occurrences of the same phenomenon. Indeed, when text is made smaller and bigger, unnecessary tags are left behind as well.
I don't use Composer so I cannot check this bug. Rob, are you still seeing it in SeaMonkey 1.1.9 from http://www.seamonkey-project.org/ ? Or on Sm 2.0a1pre from http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/ ?
It looks like nothing has changed in the 1.1 series. I did not check 2.0. You can check it using the "Steps to reproduce". Just write some gibberish in an empty composer window, select a word and bold it, then delete the word and look in the source tab.
(In reply to comment #4) > It looks like nothing has changed in the 1.1 series. I did not check 2.0. > You can check it using the "Steps to reproduce". Just write some gibberish in > an empty composer window, select a word and bold it, then delete the word and > look in the source tab. > I must be stupid: I've never used Composer before and it doesn't look like I'm going to use it in the future -- whatever I do to that Composer window, I can't get _any_ text to show up.
Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9pre) Gecko/2008041601 SeaMonkey/2.0a1pre Mandrake2008.0-PowerPack: GNU/Linux-2.6.22.18-desktop-1mdv #1 SMP Mon Feb 11 13:53:50 EST 2008 i686 Intel(R) Pentium(R) 4 CPU 2.53GHz affirmative: <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> <title></title> <meta content="Barry Edwin Gilmour &lt;barry.gilmour@bigpond.com&gt;" name="author"> </head> <body> Mary had a little lamb<span style="font-weight: bold;"></span><br> and every where that Mary went<br> that lamb was sure to go!<br> </body> </html>
Confirming (I don't use Composer but two people were hit) and adding Version + Whiteboard.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [trunk and 1.8 Branch]
Version: unspecified → Trunk
Assignee: composer → nobody
QA Contact: composer
Whiteboard: [trunk and 1.8 Branch]
Can't reproduce on trunk, feel free to reopen, if you still see this User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1 Build identifier: 20120712003002
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Confirming on Linux Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1 ID:20120714003024
Whoops~ Confirming fixed, i.e. nil artefact remnants (on Linux) Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1 ID:20120714003024
You need to log in before you can comment on or make changes to this bug.