V-cloak of Invisibility

Don't flash your users...


Something nearly all MVVM and binding frameworks have in common is the dreaded "flash of content" (FOC).

As your Vue instance finishes instantiating a page may quickly show your un-compiled mustache bindings before Vue has a chance to populate the variables. It can also have a jarring effect when "v-if" and "v-show" are being used within your Vue template.

Luckily Vue comes with an eloquent solution to the FOC problem right out of the box with "v-cloak"

V-cloak is a simple directive added as an attribute to an element that will be removed once your Vue instance has finished compilation.

It's as simple as:




<div v-cloak>



{{ foo }}



</div>

Now all that's left if to add a rule for the cloaking attribute within your styles.





[v-cloak] {



    display: none;



}

In this example the <div> will not be visible until the compilation is done.

You're now on your way to properly hiding content that still waiting to be rendered.

Have fun!

Comments

Post a Comment

Popular posts from this blog

Vue Broadcasting (Part 1)

Broadcast across all Vue instances Vue comes with the very handy feature of broadcasting events through the   $on   and  $emit  instance methods. Generally this is used to communicate between parent and child components. However, often times developers will attach an instance to the global  window  object to be able to communicate across all Vue instances. This is a great convenience but let's create a more scoped and portable solution by simply creating an exported VueEvent class: class VueEvent {     /**      * Event broadcaster class constructor.      *      * @constructor      */     constructor () {         this.vue = new Vue();     }     /**      * This will emit a broadcast that can be utlized by an active Event listener.      *      *...
Read more

Vue.js: Automatically Import Components

Automatically import all single file components during Webpack 2 bootstrap   Many developers using Webpack and utilizing Vue's Singe File Components load each component manually, one-by-one within an app or bootstrap file. However, Webpack comes with configuration options that can automate this process by instantiating the Vue component to match the file name. Let's take a look at our simple Webpack config function that can be used to automatically require our components. // Require and instantiate our components function requireAllComponents(requireContext) {     let keys = requireContext.keys();     return requireContext.keys().map(key => {         let pathMap = key.split('/'),             label = pathMap[pathMap.length - 1].slice(0, -4).replace(/([A-Z])/g, '-$1').slice(1).toLowerCase();         Vue.component(label, requireContext(key));     }); } N...
Read more

Vue.js vs Angular 1.0 (Part 2)

Which is better Vue.js or Angular 1.0 (Part 1)? Let's take a basic look at Vue.js vs. Angular: Components and Directives One of the biggest complaints from users of Angular 1.0 was the muddy nature of service providers and when to use which for what. Services, Factories, Providers, Directives, Components - there never seemed to be a clear, concise answer on how they should be used. With Vue, you have components and directives. With Vue there are components and directives, and the dilineation is very clear. WINNER:  Vue.js Community Support While Angular used to be the hottest framework around, it slowly started fizzling out as talks of Angular 2.0 came around, and React entered the scene. Many of the popular libraries are no longer updated and Vue seems to be taking its place. WINNER:  Vue.js Speed and Performance In benchmark tests, Vue outperforms Angular 1.0. With all the dirty checking and constant watchers, your Angular application will...
Read more