Waylan Limberg

@MaddyGuthridge XSS is a real and serious issue for Markdown, but it outside the scope of a Markdown parser to handle. The issue is explained in detail by Michel Fortin...

> Having to use `# type: ignore[override]` just to silence a bug coming from a dependency is frustrating and should not be necessary. This is a matter of perspective. From...

I am closing this as we have not received the requested feedback. We can reopen the issue if more information is provided.

Our behavior matches exactly the reference implementation (markdown.pl). Specifically, we treat `` as an inline tag because the reference implementation does. As the tag is deprecated, I'm inclined to not...

@facelessuser summed up my position quite well. As it is deprecated, I could care less if it is broken or not. I personally have no inclination to spend any time...

Note that the original request is an upstream issue. The extension loading code is part of the Markdown library, not part of MkDocs. All MkDocs does is accept a bunch...

> as far as I know the YAML standard says nothing about loading Python modules, True, but the Python implementation (PyYAML) adds some [features](https://pyyaml.org/wiki/PyYAMLDocumentation#yaml-tags-and-python-types) on top of the standard YAML...

After giving this some more thought, I have a proposal: # My Proposal Add a `--scripts` (or `--scripts-dir` or `--user-scripts`?) command line option to the `build` and `serve` commands. By...

Another pro of my proposal is that users would have the freedom to put their scripts dir wherever they want it. It could be a sibling of the config file...

The more I think about it, the more uncomfortable I am with the idea that the script dir path would be relative to the config file. That would be very...