Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New headless mode in chrome
Chrome has new headless mode (https://developer.chrome.com/docs/chromium/headless) activated as default since v128. This PR set back to
--headless=oldto revert back to old mode we know is working ok. There is a newQUARTO_CHROMIUM_HEADLESS_MODEenv var to configure this. This is to fix #11135.Tested with
This now renders ok under this PR.
If
QUARTO_CHROMIUM_HEADLESS_MODE=newis set and a chrome browser is already opened. Then #11135 will reproduce. close any browser open and keepQUARTO_CHROMIUM_HEADLESS_MODE=new, and issue disappear. So definitely some adaptations to make for new headless mode. As long as we can use,oldthen we can wait.Avoid blocking problem by allowing selecting the chromium binary to use
This PR introduce also a new
QUARTO_CHROMIUMto specify which binary to use and not let Quarto detection applies. closes #10170 (which closes #2980 and closes #4648)Currently I am testing our bundled
quarto install chromiumversion to see if this still work and if it is ok with this change. This is quite an old pinned version.Also, I noticed on windows that chrome opened for screenshot does not close... So investigating that too.