1.4 to 1.5 Regression - Flickering issue when using ng-show/ng-hide

Overview of the Issue -
Today i updated AngularJS 1.4 to AngularJS 1.5 and i noticed a flickering issue when loading the application with hidden ng-show/hide elements (see video)
Angular Version(s) - Regression from 1.4 to 1.5
Browsers and Operating System - Chrome 48.0.2564.97 (64-bit) MacOS 10.11.3 (15D21)
Reproduce the Error - See video

https://monosnap.com/file/d7ULotSANvDOqi7MEmIPYerZ1xH1O6
hints: I'm refreshing the pages multiple times switching between angularjs 1.4 and 1.5. Take a look at the element that appears under the search box when using 1.5 and the clear search element that appears right from the filter chapters... box although it should be hidden

When refreshing the page the ng-hide / ng-show elements are shortly visible on pageload in 1.5 (before angularjs doesn't compile the directives ?)

Suggestion: Quick fix is to use ng-if instead of ng-show/hide until the bug is fixed

[Narretz]

Thanks for the report. Can you the following for us:

1. Please check all versions of 1.4.x to see in which version the error first occurs (all changes from 1.5 are in 1.4)
2. Please reproduce the error in a plnkr.co or similar. Focus on the structure of the DOM (e.g. does the element that should be hidden have parent elements that are also animatable?)

[m-amr]

Did you try ng-cloak
https://docs.angularjs.org/api/ng/directive/ngCloak

The ngCloak directive is used to prevent the Angular html template from being briefly displayed by the browser in its raw (uncompiled) form while your application is loading. Use this directive to avoid the undesirable flicker effect caused by the html template display

I think all angular apps (that doesn't use ng-include to load template)
should use ng-cloak to prevent to hide all templates until angular compiles it.

Just did it sorry. 1.4.4 is fine the bug occurs for the first time in 1.4.5. I tried to reconstruct it in plnkr.co without success i will try it tomorrow again.
I will check tomorrow if the html components have CSS animatable if you meant that.

With ng-cloak it just flickers differently when i put it on different elements

[Narretz]

No, I actually just mean if they use directives that are animatable, such as ng-if, ng-class

I isolated a part of the code:
http://i.imgur.com/ClrMirj.png

A parent contains a ng-class but even when i remove it, the problem still persists!

I will try to make a plnkr during the day.

[Narretz]

ngShow and ngHide are also considered class based animations, so they will also add rAF spacing.

Ok i found the issue ! :) Sorry it was my fault i didn't update the angular-animate to the latest version (it was 1.4.X). Maybe it fixes @havenchyk issue too