Angularjs – ng-cloak/ng-show elements blink

Angularjs – ng-cloak/ng-show elements blink

I have an issue in angular.js with directive/class ng-cloak or ng-show.
Chrome works fine, but Firefox is causing blink of elements with ng-cloak or ng-show.
IMHO it’s caused by the converting ng-cloak/ng-show to style=”display: none;”, probably the Firefox javascript compiler is little bit slower, so the elements appears for a while and then hide?



Solution 1:

Though the documentation doesn’t mention it, it might not be enough to add the display: none; rule to your CSS. In cases where you are loading angular.js in the body or templates aren’t compiled soon enough, use the ng-cloak directive and include the following in your CSS:

  Allow angular.js to be loaded in body, hiding cloaked elements until 
  templates compile.  The !important is important given that there may be 
  other selectors that are more specific or come later and might alter display.  
[ng\:cloak], [ng-cloak], .ng-cloak {
  display: none !important;

As mentioned in the comment, the !important is important. For example, if you have the following markup

<ul class="nav">
  <li><a href="/foo" ng-cloak>{{bar}}</a></li>

and you happen to be using bootstrap.css, the following selector is more specific for your ng-cloak‘ed element

.nav > li > a {
  display: block;

So if you include a rule with simply display: none;, Bootstrap’s rule will take precedence and the display will be set to block, so you’ll see the flicker before the template compiles.

Related:  How to show a loading indicator in React Redux app while fetching the data? [closed]

Solution 2:

As mentioned in the documentation, you should add a rule to your CSS to hide it based on the ng-cloak attribute:

[ng\:cloak], [ng-cloak], .ng-cloak {
    display: none;

We use similar tricks on the “Built with Angular” site, which you can view the source of on Github:

Hope that helps!

Solution 3:

Make sure AngularJS is included in the head of the HTML. See ngCloak doc:

For the best result, angular.js script must be loaded in the head
section of the html file; alternatively, the css rule (above) must be
included in the external stylesheet of the application.

Solution 4:

I’ve never had much luck using ngCloak. I still get flickering despite everything mentioned above. The only surefire way to avoid flicking is to put your content in a template and include the template. In a SPA, the only HTML that will get evaluated before being compiled by Angular is your main index.html page.

Related:  Why is this simple AngularJS ng-show not working?

Just take everything inside the body and stick it in a separate file and then:

<ng-include src="'views/indexMain.html'"></ng-include>

You should never get any flickering that way as Angular will compile the template before adding it to the DOM.

Solution 5:

ngBind and ngBindTemplate are alternatives that do not require CSS:

<div ng-show="foo != null" ng-cloak>{{name}}</div>  <!-- requires CSS -->
<div ng-show="foo != null" ng-bind="name"></div>
<div ng-show="foo != null" ng-bind-template="name = {{name}}"></div>

Solution 6:

In addition to the accepted answer if you’re using an alternative method of triggering ng-cloak…

You may also wish to add some additional specificities to your CSS/LESS:

[ng\:cloak], [ng-cloak], [data-ng-cloak], [x-ng-cloak],
.ng-cloak, .x-ng-cloak,
.ng-hide {
    display: none !important;