Yahoo Cache Bug?

Cache Messing up my site's <sup> tags

[Jordo needs a drink]

On one of my sites, I use the html <sup> tags quite frequently. Like so <a href="example.com">¹</a>

The pages do validate, and no search engines have a problem with it, except that the yahoo cache converts it to <a href="example.com"> <sup>1&lt;/sup&gt;&lt;/a&gt;

This severely messes up how the cached page looks and acts. Anyone else see this?

[Jordo needs a drink]

No one else has seen this?

I ended up having to get rid of the html sup tags and use css to get the sup effect on the page. That seemed to work ok, because now the pages show up fine when viewing their cache's.

[jdMorgan]

Yup, I see the same problem in an even simpler context. I'm using markup like ¹ in <ul><li> text (not linked as in your example) for citation lists on some old pages, and it renders on the cached page as:

Smith et. al<sup>1

This is sort of the opposite of what you're seeing; In your case it was the </sup> closing tag that got changed to HTML character-entities. In my case, it was the opening <sup> tag. Because of this difference in our applications, it looks like a problem handling <sup>s nested within other tags.

So that's a confirmation of what appears to be a fairly straightforward bug.

Jim

[Tim]

Can you send me a few examples of this post the recent update we did so we can diagnose this and fix it.
Thanks, Tim

[surftrack]

i've also noticed issues with having an inline style tag inside the <a> tag

if the style is in front of the href part of the tag, then the cache spits out the whole <a> tag instead of showing a link.(not sure if you use the cache to spider or count links...if so, that could be a major issue with your link part of the algo)

i will look for and sticky you an example.

[Tim]

Thanks for the examples we are looking into this.
Tim