Attribute Removed When Post is Listed in a PerlMonks Section

[kcott]

Background

Last week I wrote Syntax-highlight Non-Perl Code for HTML which I posted in Cool Uses for Perl.

The first line contained the abbreviation CRPG. I provided a tooltip for this using the title attribute, like so:

<span title="Computer Role Playing Game">CRPG</span>

The tooltip showed up in both the [preview] and [create] renderings. Everything looked fine and I thought no more about it.

That post was front-paged and I've just noticed that the version in The Monastery Gates listing (under New Cool Uses for Perl) had no tooltip for CRPG.

I checked the source HTML in Syntax-highlight Non-Perl Code for HTML which had, as expected:

<span title="Computer Role Playing Game">CRPG</span>

I then checked the source HTML in The Monastery Gates which had, not as expected:

<span>CRPG</span>

And now, while previewing this post, I also notice that the listing in Cool Uses for Perl has no tooltip either (source HTML: <span>CRPG</span>).

That's now potentially becoming somewhat confusing. To summarize (and clarify):

Node ID	Node Name	Tooltip	Source HTML
1132421	Syntax-highlight Non-Perl Code for HTML	Yes	<span title="Computer Role Playing Game">CRPG</span>
131	The Monastery Gates	No	<span>CRPG</span>
1044	Cool Uses for Perl	No	<span>CRPG</span>

So, while that's two PerlMonks Sections that I was able to check, this could also be happening in other sections.

Questions

Is the title attribute (and value) intentionally removed from the listings in PerlMonks Sections? If so, what is the rationale behind this? Are attributes other than title affected? Are elements other than span affected?

If this attribute was not intentionally removed then, presumably, that indicates a problem somewhere in the process of listing a post in various PerlMonks Sections. If this is the case, can it be fixed?

[LanX]

Let's summarize for the TL;DR-people: ;-)

Your post was front-paged and there (The monastery gates) the title-attrribute was disabled.

I just checked and you are right, the opening span-tag is marked as an HTML error there (it's an option in my display settings)

Strange, I never thought that renderers might be different.