I've already fixed this on our end as we were already using a custom footer parser. Here's a workaround, note that the parser regex here is our custom one (not the default one) as we have a wider ...

No validations are performed, a valid RegExp object mut be provided, so validation is delegated to the engine. The AST produced is not a "concrete" AST, but you could reconstruct a RegExp equivalent ...