Aurélien Chivot-Buhler

Same issue here in v33.0.1750.152. By logging the `getComputedStyle` content in the console, we can see that the value is fine, so it is definitely a race condition. Only in...

I just proposed a PR for anyone who wants a quick fix. Instead of bulky workwround above, i just added a timeout in the descriptor : ``` $timeout(function() { return...

This is crazy, even with the timeout it breaks sometimes. I even had to add a real delay like 100ms (as $timeout function param) in some case, it does not...

**Followup to my previous comment:** I made a codepen to better understand the issue. It happens that `getComputedStyle` for the pseudo `:before` element might not be ready in specific cases,...

Seem related to [this anguar issue](https://github.com/angular/angular.js/issues/2151). I tried the mentioned workaround which is to wrap `ng-repeat` element if it is the card's root element, but with no success...

As a quick workaround, for anyone interested, here is a very basic directive to replace `ng-repeat` and that does not creates a new scope while iterating through card items ```...

Until this PR is merged, I've been able to workaround this by calling the following when I want to recompute height manually: ```js // Recompute height this.swipeableViewsRef.current .getChildContext() .swipeableViews.slideUpdateHeight() //...

Do you mind sharing your concern about the suspecte regression? It felt that this code was modifying only the animateHeight scope of this component. Anyway I guess more tests are...

I see someone opened a SO question here as well: https://stackoverflow.com/questions/60960230/cant-see-the-item-that-i-am-dragging-using-react-dnd

FYI, I also had an empty `` markup in the _server_ render, until I downgraded to 1.0.0-rc2 btw thank for the workaround ;)