Juhan Oskar Hennoste

> It does. It would interesting to test 5 GHz. You can easilly change the list of channels in the original script. This should be a pretty representative sample of...

> Let me know what else I can test for you. I don't currently have any ideas for specific adapters to test. What I would really appreaciate is some kind...

> This is dependent on the [`output_format`](https://python-markdown.github.io/reference/#output_format). Python-Markdown defaults to outputting XHTML for historical reasons and an attribute without a value is not valid XHTML. However, if you change the...

I specifically meant that modern browsers treat `download` as equivalent to `download=""` in HTML. It is specified here in the spec for all attributes:  https://html.spec.whatwg.org/#attributes-2S For XHTML attributes without...

I don't quite understand what you are asking for. I am certain even without reading the spec that XHTML supports `download=""` and I don't see what else in the XHTML...

Both are valid. My problem is that currently switching from XHTML output to HTML output changes the meaning of the generated HTML/XHTML document.

`[download](file.txt){download}` is rendered as `download` in XHTML, but `download` in HTML. These produce different behavior in the browser. My proposal would correct this inconsistency.

> Browsers only recognize XHTML as XHTML if the proper doc type is defined. AFAIK in modern browsers XHTML and HTML just have syntax and validation differences. (I couldn't find...

> And that means that if someone actually wants download="download", the suggested change would make that impossible. I think it's worth noting that this issue already exists for the HTML...

I have a similar need and what I settled on is doing something like this: ```python try: browsers.append(rookiepy.safari) except AttributeError: pass # Presumably on a platform that does not have...