Wt

While trying the latest updates I discovered that WT-13501, namely Commit 05e4064, introduces a breaking bug with WTemplate internal path encoding. Having an <a> tag inside a condition block, like ${<cond>}<a href="#/target">link</a>${</cond>}, will lead to a javascript exception if internal path encoding is enabled and the condition is set to false.

I could trace the issue to the changes in RefEncoder.c. Despite the <a> tag not being included in the (rendered) template text due to the false condition, the newly introduced javascript will be created and executed regardlessly - but will not find an element with the dummy id and thus result in the aforementioned javascript exception. Interestingly this issue does not always seem to occur on inital page loading. It does occur though, if the WTemplate is added later in an event.

I created and added a minimal working example. Just start it up in an ajax enabled session, click the button and enjoy! :)