bug(CDK): Drag and drop: Cannot read properties of null (reading 'style')

[anton-white]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Hi guys,

We are constantly facing production issues reported by Sentry.
Here is the screenshot:

The problem occurs on https://github.com/angular/components/blob/main/src/cdk/drag-drop/dom/styling.ts#L77C18-L77C18

It looks like it happens on Chrome OS only:

Affected browser versions:

This is a real problem for us, because this error crashes the entire app and users have to refresh the browser and sign in again to bypass it.

Please hint us where to look at.

Reproduction

Unfortunately we cannot reproduce this error locally. Neither we were able to identify conditions that are causing it.

Expected Behavior

No error and no browser crash.

Actual Behavior

Error and browser crash.

Environment

Angular CLI: 16.2.0
Node: 18.16.0
Package Manager: npm 9.6.6
OS: darwin x64

Angular: 16.2.1
... animations, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1602.0
@angular-devkit/build-angular   16.2.0
@angular-devkit/core            16.2.0
@angular-devkit/schematics      16.2.0
@angular/cdk                    16.1.4
@angular/cli                    16.2.0
@angular/material               16.1.4
@schematics/angular             16.2.0
rxjs                            7.8.1
typescript                      5.1.3
zone.js                         0.13.0

[crisbeto]

Can you provide information on how to reproduce the issue?

[anton-white]

Can you provide information on how to reproduce the issue?

Unfortunately we weren't able to reproduce it locally. We have Sentry replay recording only and they show an issue is likely happening on the drop event.

[mmalerba]

Closing since we are unable to reproduce

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}