Quarto code and options use terms blacklist and whitelist

[lachlansimpson]

Bug description

Quarto uses the terms whitelist and blacklist.

quarto-cli/src/resources/editor/devserver/devserver-core.html

Line 205 in 85c9e30

this._url_whitelist = { 'http': 1, 'https': 1 };

quarto-cli/src/vendor/cdn.skypack.dev/-/[email protected]/dist=es2019,mode=imports/optimized/ansi_up.js

Line 55 in 5bfd772

this._url_whitelist = {http: 1, https: 1};

quarto-cli/src/resources/formats/html/bootstrap/dist/scss/vendor/_rfs.scss

Line 1 in d16d9f1

// stylelint-disable property-blacklist, scss/dollar-variable-default

Checklist

• Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
• Please format your issue so it is easier for us to read the bug report.
• Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
• Please document the operating system you're running. If on Linux, please provide the specific distribution.

[cscheid]

Yes, these are very problematic terms. But they come from dependencies that we don't control, so we can't fix them.

[lachlansimpson]

For future reference, I see that the first two references are to whitelist in anso_up.js. An issue has been opened against their repo here: drudru/ansi_up#71

The reference to blacklist is in Bootstrap, and is upstream to them in stylelint:

• Bootstrap removes language [RFC] Remove blacklist and other oppressive terminology twbs/bootstrap#31064
• Bootstrap PR: Change "whitelist" to "allowlist" twbs/bootstrap#31066
• stylelint removes language: https://github.com/stylelint/stylelint/releases/tag/13.7.0

[lachlansimpson]

Hi @cscheid I see that Bootstrap has updated to remove blacklist and that ansi_up removed whitelist in a commit on Aug 15.

Is it possible for these changes to be imported to Quarto now? Thanks!

[dragonstyle]

We have updated our bootstrap dependency in Quarto 1.4 and it incorporates this change. Leaving open as I believe that we still have the issue with anso_up.js.

[lachlansimpson]

@dragonstyle thank you - is that because more testing is needed before using the latest version of anso_up.js?

[dragonstyle]

No I'm just not that familiar with our use of ansi_up. I will take a closer look soon.