9382

The issue seems to arise from the regex used for finding and removing the protection template ([twinkleprotect.js#L1447](https://github.com/wikimedia-gadgets/twinkle/blob/master/modules/twinkleprotect.js#L1447)) checking for whitespace on both sides of the main template finding The rough...

>This bug may be specific to the "noinclude" code path Indeed it is The specific cause of this issue seems to arise from [twinkleprotect.js#L1487](https://github.com/wikimedia-gadgets/twinkle/blob/master/modules/twinkleprotect.js#L1487) (and the code for other content...

@SpinnySpiwal I've tried reducing this down to the simplest case I can. Hilariously enough, some of the code samples I generated using the Medium preset triggered the `Tamper Detected!` error...

> It works with my custom preset and obfuscation steps. And it also works with mine *the majority of the time*. I've said this isn't a guaranteed error, you need...

Anti tamper isnt the issue here. The VM is unable to handle certain `repeat until`s since it doesn't correctly handle how locals work in them. Any local defined during the...

Obfuscating just the line you provide doesn't cause me any issues. If you are, however, using the `Strong` preset, that uses the AntiTamper step, which relies on the debug library,...

The template {{More footnotes needed}} currently produces the css class `box-More_footnotes` instead of `box-More_footnotes_needed`, meaning that when `Twinkle.tag.alreadyPresentTags` is populated, it populates it with the name of the redirect to...

I'll also note I've just seen #1618 which appears to be the exact same bug