Closed seocam closed 11 years ago
Just found out that the problem isn't actually with the data-* attributes but with the JSON stored inside it. The XSL template tries to interpret the empty {}
as an XPath expression and obviously that won't work.
Doing a quick search I found that attributes with curly brackets can be safely set using <xsl:attribute>
[1].
Is it worth to add some kind of treatment for that on compile_theme
?
[1] https://mikewest.org/2007/06/escaping-curly-braces-in-xslt-attributes
Closing in favor for pull request #22
I'm trying to use a theme that has the following tag:
I've tried to use html5lib and subclass etree.HTMLParser and htm5parser.HTMLParser creating an HTML parser that supports HTML5 and also can be passed as argument to etree.parse. The parser actually worked but it didn't fix my bug since the problem is happening during transformation and not parsing. Here is where the problem happens:
Are there any params that could help me here?
Unfortunately stripping data-* attributes is not an option for me.