in reply to Re^5: Add < /br> to Approved tags? (rub)
in thread Add < /br> to Approved tags?

Tye I give this a major ++.

However I am not sure I understand your third paragraph as you intended. My confusion stems from this:

Regxp: signaling when to stop and Re: use lib functionality are the latest among the June-to-date nodes which use "</br>."

In the case of the second (for its brevity), the opening line(s) render this way (color and font excepted), for me, in IE6, FF & Moz:

Hi,</br></br> This Module simplifies the manipulation of @INC at compile time.</br></br> Using

When observed with ViewSource (html validator is on), I see:

<p> Hi,<font color="#808080" class="htmlignored">&lt;/br></font><font colo +r="#808080" class="htmlignored">&lt;/br></font> This ...</p>

Is this an indication that the </br> tags were processed by an existing "silent (and automated) transformation" or merely an artifact of the browser, ViewSource and the validator?

Replies are listed 'Best First'.
Re^7: Add < /br> to Approved tags? (rub)
by tye (Sage) on Jun 20, 2007 at 22:19 UTC

    No, IE and FireFox don't render ­&lt;/br> the same as <br />. They render </br> as if it were <br /> (and even render <br></br> as if it were <br /><br />). If you want to use PerlMonks to test that, then turn off HTML nesting enforcement so that the browser will see </br> (not &lt;/br> or nothing).

    HTML nesting enforcement will remove and/or add tags to attempt to make the node well-formed so it won't impact the display of surrounding material. If you have its error reporting turned up high enough, then it will also add greyed-out information about what was removed or added. So the original (invalid) </br> is removed by it and, for you, a greyed-out version is inserted so the transformation is not "silent" in this case.

    It is sad that "view source" (in the case FireFox, at least, last I checked) doesn't always faithfully show the source that it received so that people are left guessing.

    - tye