• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • Jenkins 2.429 and above
      Firefox 120.0

      Hi,

      After updating Jenkins from 2.420 to 2.429 (and above ) pop-up menus in Jenkins became transparent when using Firefox browser, could you please fix that?

      Steps to reproduce:
      1. Open/Create a pipeline
      2. Enable "This project is parameterized" in General section, or "Use secret text(s) or file(s)" in "
      Build Environment"
      3. Press Add button to add a parameter/secret
       
      Expected results:
      Menu with clear items selection is shown

      Actual results:
      Transparent menu is shown, where items are overlaying the background.
       
      Additional info: tooltips seems affected too, see the 3rd screenshot.
       
      In Chrome-based browsers menu renders correctly with some fancy transparency to the edges (Chrome-only styling?)
      css class for those items is .jenkins-dropdown, looking into source code I see this commit, which may be related
      https://github.com/jenkinsci/jenkins/commit/0c71e4105cb5d5301d45b42a16f511c6df30034c
       
       
       

        1. Chrome.PNG
          Chrome.PNG
          41 kB
        2. Firefox1.PNG
          Firefox1.PNG
          39 kB
        3. Firefox2.PNG
          Firefox2.PNG
          46 kB
        4. Firefox3.PNG
          Firefox3.PNG
          9 kB

          [JENKINS-72410] Dropdown menus are transparent in Firefox

          Mark Waite added a comment -

          px I can't duplicate the problem as reported. I'm using Jenkins 2.434 with Firefox 120.0.1 (64 bit) on a Windows 11 computer running most recent operating system patches. Can you provide more details about the environment where you see the issue?

          Mark Waite added a comment - px I can't duplicate the problem as reported. I'm using Jenkins 2.434 with Firefox 120.0.1 (64 bit) on a Windows 11 computer running most recent operating system patches. Can you provide more details about the environment where you see the issue?

          Px added a comment -

          Sure. Jenkins is installed on Ubuntu VM as an apt package, so from this side all should be ok.

          Browser is running inside a Windows 10 Pro VM with no hw acceleration for graphics. I've tested a clean profile, and the issue is present, so it is not related to addons.

          What else could be shared here?

          Px added a comment - Sure. Jenkins is installed on Ubuntu VM as an apt package, so from this side all should be ok. Browser is running inside a Windows 10 Pro VM with no hw acceleration for graphics. I've tested a clean profile, and the issue is present, so it is not related to addons. What else could be shared here?

          Mark Waite added a comment -

          If it is a Windows 10 Pro VM, then that may indicate you are using some form of remote desktop client to access the virtual machine? If not a remote desktop client, then possibly some other form of display sharing technique that may be causing the issue?

          Mark Waite added a comment - If it is a Windows 10 Pro VM, then that may indicate you are using some form of remote desktop client to access the virtual machine? If not a remote desktop client, then possibly some other form of display sharing technique that may be causing the issue?

          Px added a comment -

          Yes, it is RDP connection with full desktop experience. No issue with previous Jenkins version, and no issue in Chrome.

          Px added a comment - Yes, it is RDP connection with full desktop experience. No issue with previous Jenkins version, and no issue in Chrome.

          Px added a comment -

          I've run additional tests to see when this was broken. 2.421 is ok, 2.422 is bad, so https://github.com/jenkinsci/jenkins/pull/8418 is indeed a culprit here.

          I've also run tests from local machine without RDP to this deployment, and can confirm that menus are rendered correctly in Firefox with both hw acceleration enabled and disabled.

          Thus is could be some issue in Firefox rendering. I've searched their bug tracker for Jenkins/Transparent menus/rdp, but didn't find anything relevant. To confirm if this is the case, I need a test case to check, but I'm not a html/css person, and if I just save Jenkins page in browser, pop-up menus are not working on saved page

          Px added a comment - I've run additional tests to see when this was broken. 2.421 is ok, 2.422 is bad, so https://github.com/jenkinsci/jenkins/pull/8418 is indeed a culprit here. I've also run tests from local machine without RDP to this deployment, and can confirm that menus are rendered correctly in Firefox with both hw acceleration enabled and disabled. Thus is could be some issue in Firefox rendering. I've searched their bug tracker for Jenkins/Transparent menus/rdp, but didn't find anything relevant. To confirm if this is the case, I need a test case to check, but I'm not a html/css person, and if I just save Jenkins page in browser, pop-up menus are not working on saved page

          Mark Waite added a comment -

          Deeper analysis of the failure mode is included in JENKINS-72430

          Mark Waite added a comment - Deeper analysis of the failure mode is included in JENKINS-72430

            Unassigned Unassigned
            px Px
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: