<script> proprietary attribute "nomodule"

[haroldwbe]

this attribute is (only recently) supported by all major browsers

and code like this will (imo) be very common in the future:

<script type="module" src="module.js"></script> <script nomodule src="fallback.js"></script>

or

<script nomodule="nomodule" src="fallback.js"></script>

[geoffmcl]

@haroldwbe, thank you for the issue, but wow, I do not know how, why, this issue failed to attract attention, for years!!!

Interestingly, there is a w3c issue - Should support nomodule attribute on script elements 314 - bzbarsky opened this issue on May 4, 2017

A quick Living Standard check certainly shows the nomodule boolean attribute...

Seek more W3C refs/specs, but assuming it is a valid W3C script attribute... a small sample I created, using the above snippets, passed the W3C validator...

Tidy's current supported script attributes does not yet include nomodule!

In fact there is no TidyAttr_NOMODULE enumerated in tidyenum.h, so that would need to be added, then defined in attrs.c, attrdict.c, ...

The process is described in ATTRIBUTES.md docs...

Although I disagree with "Please try to keep this enumeration in alphabetical order." stated there. A new attribute needs to be added to the end of the list, just before N_TIDY_ATTRIBS, unless we are prepared to bump the SO version at the same time... read #851...

I will try to find the time to add a PR for this... unless someone beat me to it... need some help here...

Again sorry this got overlooked... but better late, than never ;=))

Look forward to further feedback, comments, patches, PR, etc, etc... thanks...