Macro Customisation at various levels

Currently macro's like

{html} can either be enabled fully or not at all. This request is for macro's to have runtime options which can be set at the global / space / page level to pass in variables for configuration.

Using the {html}

macro as an example - this is a dangerous macro but customisation at any could be used to secure what tags can / cannot be used inside the macro [eg: disable <script /> tags]. In some cases you might only want <table> based elements (tr,td,th etc) to be used in a documentation space when greater flexability than the simple wiki tables are needed.

If the allowed list is populated, ONLY those tags should be allowed, if the denied list is populated ANY tags except those listed should be allowed, if both lists are empty then all tags should be allowed (default behaviour).

The customisations / configurations should be allowed to inherit and override, inherit only, or replace unilatterally the configurations from the container above (eg: in the space set whether these configurations can be overriden / inherited by pages, and on a page set what you want to do [where allowed])