BUG REPORT: colour is improperly remembered for SIG
 

When using the html commands to change font colour, the SIG tends to re-use the first changed colour (by mistake) even though the colour is later on changed back to default black.

F O L L O W U P E X A M P L E
 

<font color=red>This sentence uses red colour.<font color=black> And now the default colour is changed back to black. However, the SIG will use the red colour for regular text instead of the default black.

Looking at the HTML, it's not a bug -- you're just not closing the first font tag.

I'll do my own test really quickly:

<font color="#ff0000">This is red.</font> <font color="#000000">This is not.</font>

Sho' 'nuff. Not a vBulletin bug.

vBulletin automatically closes any post with an open font tag, but it only closes <b>one</b> set.

I'm guessing this is what you typed in:

The <i>proper</i> HTML would be as follows:

The software does a pretty good job at fixing most people's bad HTML, but it can't work miracles. :)

I am curious
 

<font color=orange>Why should the first font colo(u)r tag be remembered in the sig (as demonstrated above) and not the second?

Isn't one of the features of the software that it is said to close tags left unopened in the body text?</font>

benedict: As I explained above, vBulletin will close an unclosed font tag. It doesn't close two.

Look at it this way:

Here's the original text. vBulletin sees an unclosed font tag and closes it.The web browser takes the portion in bold and makes it black, as the HTML code specifies.The 'font color=black' is now closed, but the 'font color=red' remains open. vBulletin handles mistakes pretty well, but it isn't designed to look for every possible error someone unskilled in HTML can possibly make.

<font color=red><font color=blue>an apparantly irate ctyner posted:
vBulletin handles mistakes pretty well, but it isn't designed to look for every possible error someone unskilled in HTML can possibly make.<font color=black>

*wink* I had noticed that not all tags needed to be closed in the prior version. In the prior version, I would sometimes deliberately leave tags open because I knew that the next subsection of the thread being built would fix the problem.

However, not all of my assumptions for this new version of vBulletin did not hold true. Some of the assumptions are still holding though, and I still depend on the idiosyncracies to remain. To me, it is part of the "texture" of a particular web forum.

More interesting would be how many open red font tags like <font color=red>Code <font color=blue><font color=red>Red<font color=black> can remain open at a time.

Another reason why was that I sometimes insert two spaces in a row by using the font tag with something innocuous. Yes, I know you are supposed to have just one space after a period in this forum.

This sentence should be tutti-fruity coloured.

<b>ctyner</b>, yes, I see/saw what you are/were saying.

Somehow I had it in mind that (some?) browsers would treat a closing font tag as closing <i>all</i> behind it and returning to the default. I'm not sure where I picked up this notion.

Anyway, that was the reason behind my query. (oh, and also so I could do a "curious orange/yellow" visual pun: it was an old scandinavian hippy porn film!).

Thanks for responding.