Thread

I noticed today that the typography library now (as of 2.4.0) uses a unique attribute – rather than a unique ID – for email obfuscation. In other words, this…

{encode="[email protected]"}

Results in a chunk of output that starts with…

<span eeEncEmail_BYtJwXoFBg='1'>(...)

Whereas it used to start with…

<span id='eeEncEmail_BYtJwXoFBg'>(...)

This bug report explains the change, but the new attribute is invalid HTML5 according to the W3C validator. Should I submit another bug report, or is there a known workaround?

Hi Matt,

I verified that the output generated by the {encode} tag does not validate.

Feel free to file a new bug report on it, but it’s apparently working as intended, although not desirably.

Cheers,

Will do, Dan. Thanks!

I’m going to close out this thread, but feel free to post again when you have more questions.

Sean