Potentially fix system tests where content could not be found on page

[fbacall]

Summary of changes

• Disables some Chrome feature (DeferRendererTasksAfterInput) that was possibly causing it.

Motivation and context

Error was:

Error:
GroupsTest#test_should_update_Group:
Selenium::WebDriver::Error::UnknownError: unknown error: unhandled inspector error: {"code":-32000,"message":"Node with given id does not belong to the document"}
  (Session info: chrome=151.0.7922.108)
    test/system/groups_test.rb:40:in 'block in <class:GroupsTest>'
..

https://github.com/ElixirTeSS/TeSS/actions/runs/31781210426/job/94707172901#step:10:44

Even though the text appears as normal in the screenshot:

Some discussion: teamcapybara/capybara#2800

If it doesn't work, also try passing --disable-backgrounding-occluded-windows

Checklist

• I have read and followed the CONTRIBUTING guide.
• I confirm that I have the authority necessary to make this contribution on behalf of its copyright owner and agree to license it to the TeSS codebase under the BSD license.

[Copilot]

Pull request overview

Updates the Rails system test Selenium/Chrome configuration to reduce flaky “node does not belong to the document” errors seen in CI by adjusting Chrome runtime flags used by ActionDispatch::SystemTestCase.

Changes:

• Adds a Chrome command-line argument to disable the DeferRendererTasksAfterInput feature when running headless Chrome system tests.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.