Docs: Add note for Chrome 132+ regarding headless mode changes

[alcpereira]

User description

Description

This PR completes the existing notes, with the addition of Chrome v132+ that completely removes the old behaviour, meaning that you need to have SE_START_XVFB=true when running headless.

Motivation and Context

While trying recent versions of Docker Selenium, I noticed an issue with --headless and SE_START_XVFB.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

Documentation

---

Description

• Added documentation note for Chrome 132+ headless mode changes

• Clarified requirement for SE_START_XVFB=true with new headless mode

---

Changes walkthrough 📝

	Relevant files
Documentation	README.md Add Chrome 132+ headless mode and XVFB documentation note README.md Added note about Chrome/Chromium v132+ headless mode behavior Explained necessity of SE_START_XVFB=true for headless mode in v132+ +1/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[CLAassistant]

All committers have signed the CLA.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[qodo-merge-pro]

PR Code Suggestions ✨

No code suggestions found for the PR.