Alex

I feel like [this Chromium bug](https://issues.chromium.org/issues/350029229) is directly related to this issue. Considering that someone from Microsoft has filed it, do you have any updates or insight on the issue?

@peiche-jessica, I'm pretty sure that we have identified the Chromium commit that caused this regression. Please see my [comment in the bug tracker](https://issues.chromium.org/issues/350029229#comment7).

We think the root cause is the `DocumentPolicyIncludeJSCallStacksInCrashReports` origin trial that was active in [Chromium M133-M135 (inclusive)](https://groups.google.com/a/chromium.org/g/blink-dev/c/5W-TJDTz7pE/m/-cdgoRuZAAAJ) and triggered by `Origin-Trial` header on youtube.com. As this trial is not active...

@Badhri, any news about this issue? We experience it again and were forced to use `--origin-trial-disabled-features=DocumentPolicyIncludeJSCallStacksInCrashReports` in our WV2 configuration to prevent messaging breakage.

Actually, this is not related to Youtube or `DocumentPolicyIncludeJSCallStacksInCrashReports` trial. E.g.: * [autotrader.com](https://autotrader.com/) has the following active trials: `AIPromptAPIMultimodalInput`, `SoftNavigationHeuristics`. If I disable only `SoftNavigationHeuristics`, messaging starts working. I.e. `SoftNavigationHeuristics`...