[🐛 Bug]: Chrome sets opacity values to zero and elements are invisible

[betelgeuse]

What happened?

Any other CSS value then opacity gets set to zero meaning the element is invisible. Filing here first since it's very unlikely that this is a general Chrome issue (presumably it would have been spotted by the wider public).

Command used to start Selenium Grid with Docker (or Kubernetes)

selenium:
    container_name: selenium_chrome
    image: "selenium/standalone-chrome:latest"
    platform: linux/amd64
    # https://github.com/SeleniumHQ/docker-selenium?tab=readme-ov-file#--shm-size2g
    shm_size: 2G
    environment:
      SE_NODE_SESSION_TIMEOUT: 1800
      SE_SCREEN_WIDTH: 1920
      SE_SCREEN_HEIGHT: 1080
    ports:
      - "127.0.0.1:7900:7900" # VNC via HTTP
    networks:
      - internal_network

Relevant log output

Nothing interesting in docker logs selenium_chrome. Here are version numbers:

22:18:43.471 INFO [NodeOptions.report] - Adding chrome for {"browserName": "chrome","browserVersion": "136.0","container:hostname": "f18b01a17f9d","goog:chromeOptions": {"binary": "\u002fusr\u002fbin\u002fgoogle-chrome"},"platformName": "linux","se:containerName": "f18b01a17f9d","se:noVncPort": 7900,"se:vncEnabled": true} 1 times
22:18:43.510 INFO [Node.<init>] - Binding additional locator mechanisms: relative
22:18:43.546 INFO [GridModel.setAvailability] - Switching Node 80e716dc-5294-4508-b747-5608b14aa1c4 (uri: http://172.25.0.5:4444) from DOWN to UP
22:18:43.547 INFO [LocalDistributor.add] - Added node 80e716dc-5294-4508-b747-5608b14aa1c4 at http://172.25.0.5:4444. Health check every 120s
22:18:43.708 INFO [Standalone.execute] - Started Selenium Standalone 4.33.0 (revision 2c6aaad03a): http://172.25.0.5:4444

Operating System

OS X 15.5

Docker Selenium version (image tag)

745c10306dcc

Selenium Grid chart version (chart version)

No response

[github-actions]

@betelgeuse, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[sschimansky]

I have the same issue. Any element with an opacity value greater 0 and smaller than 1 becomes invisible. I tried the node-chrome / node-chromium images for testing. The node-firefox image renders opacity values correctly.

This happens even with older versions of chrome that worked fine before. I suspect that docker desktop has something to do with it.

[diemol]

Does this mean the issue only happens inside Docker and not when you use Chromium/Chrome on a regular desktop?

[betelgeuse]

Does this mean the issue only happens inside Docker and not when you use Chromium/Chrome on a regular desktop?

Correct. This is an issue filed about the Chrome behavior under Selenium inside Docker.

[sschimansky]

I switched to the node-chromium amd64 image. Suddenly everything works flawlessly. Maybe the linux/x86_64 emulation on DockerDesktop (macOS) is the problem 🤔. However no node-chrome amd64 image exists. I will stick with chromium for now.

[diemol]

Thanks for the clarification, @sschimansky.

@betelgeuse please use the images for your arch.

[diemol]

However no node-chrome amd64 image exists

Because there is no ARM Chrome binary for Ubuntu.

[betelgeuse]

@betelgeuse please use the images for your arch.

What do you mean? You only push linux/amd64 images.

https://hub.docker.com/r/selenium/standalone-chrome/tags

[diemol]

Those are images for that architecture. You have a Mac, you need to use https://github.com/SeleniumHQ/docker-selenium?tab=readme-ov-file#experimental-multi-arch-amd64aarch64armhf-images

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.