[BUG] Red Panel in the discover results panel

[dewsingh]

Describe the bug

With the latest Chrome 129 browser, the dashboards discover results pane displays a red panel in place of the result values when the results panel is expanded.

To Reproduce
Steps to reproduce the behavior:

1. Login into dashboards GUI.
2. Go to Discover UI
3. Select an index and then Scroll down to the results pane. Initially the results are displayed as expected.
   
4. Expand the results. A red panel is displayed now.
   

Expected behavior
The results panel should expand to show details of the document.

OpenSearch Version
2.12.0

Dashboards Version
2.12.0.0

Plugins

SecurityDashboards, ReportDashboards

Host/Environment (please complete the following information):

• Google Chrome Version 129.0.6668.59

Additional context

This issue is not observed in the older Chrome browser Version 128.

[ihtkas]

I am also facing the same issue. The issue is observed in Chrome and Arc browsers.

[sahil-rathi]

Facing the same issue whenever any log is expanded in legacy mode.

[DougllasLima]

I am experiencing the same issue with this version of Chrome: Version 129.0.6668.59 (Official Build) (64-bit). The issue has not been observed in Microsoft Edge.
The error occurred after I executed a DQL query through the Discover tab, where I was searching for results based on a string condition. After this, OpenSearch crashed, and when it reopened, the screen was red.
It was possible to identify that within the element .eui-xScrollWithShadows, the properties -webkit-mask-image and mask-image have all colors set to red and are checked. Removing the check makes the red screen disappear.

[Swiddis]

Duplicate: #8250

[TanweerulHaque]

I am also observing the same issue in brave browser.
CSS: .eui-xScrollWithShadows, the properties -webkit-mask-image and mask-image are set with red colors. Unchecking these properties removes the red screen.

[shachar-karry]

I use managed Opensearch by AWS.
After upgrading to Chrome 129 this begun.

I updated OpenSearch version to 2.15 (latest on AWS) and seems the problem is solved with the fix in: #8277

Thanks 🙏

[SricharanSundar]

Hi all,
I'm using Chrome Version 129.0.6668.71 (Official Build) (64-bit).
The OpenSearch is working fine for me. Using(OpenSearch 2.13 managed service)

[javad87]

I encountered this issue as well on Chrome version: Chrome is up to date Version 129.0.6668.71 (Official Build) (64-bit)
Opensearch: v 2.12.0 deployed by docker on AWS EC2 machines.

[george-kirkman]

I also encountered this issue on Chrome and Arc

• OpenSearch v 2.11.0
• Arc Version 1.61.0 (53949) (Chromium Engine Version 129.0.6668.59)

[MaxStlbv]

hey!
the same problem
OpenSearch - v 2.11.0
Chrome - Version 129.0.6668.71

[prasadjella]

I'm facing same issue in Microsoft edge browser Version 129.0.2792.65 (Official build) (64-bit)

[M-Porter]

I hate doing a "me as well" comment, but given how little traction this has over the last week... its happening to me as well.

You can use something like tampermonkey to fix it

(function() {
    'use strict';

    var styles = `
        .eui-xScrollWithShadows {
            -webkit-mask-image: none !important;
            mask-image: none !important;
        }
    `;

    var styleSheet = document.createElement("style")
    styleSheet.textContent = styles
    document.head.appendChild(styleSheet)
})();

[JViggiani]

Same issue

[dblock]

Closing as duplicate, please add any comments to #8250

[dblock]

[Catch All Triage - 1, 2, 3, 4]