You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DOMPurify appears to be well-maintained and has an up-to-date allowlist. Explore using those allowlists instead of the HTML5lib-derived lists currently used by Loofah.
determine how well whitelists match up to the currently-used-set
determine how big the diff is
look at using IS_ALLOWED_URI to allowlist protocols
make sure to include the DOMPurify license in any machine-generated file
consider making a separate gem for Loofah's allowlist and inject it into Loofah by default
... and then document how anybody else can modify or inject their own allowlists, which should address a lot of open issues (see the allowlist label)
... and deprecate Whitelist in preference to Allowlist, exploring how to do so without totally breaking monkeypatches people may have made to Loofah's allowlists.
DOMPurify appears to be well-maintained and has an up-to-date allowlist. Explore using those allowlists instead of the HTML5lib-derived lists currently used by Loofah.
IS_ALLOWED_URIto allowlist protocolsallowlistlabel)Whitelistin preference toAllowlist, exploring how to do so without totally breaking monkeypatches people may have made to Loofah's allowlists.