ajax - Motivation behind AngularJs's data-ng-include - poor UX -
in angularjs can this:
<header data-ng-include="views/header.html"></header>
which afaik asynchronously downloads views/header.html
client , interprets template.
i want ask if there sane motivation use because encountered pretty bad usex experience. have black twitter bootstrap header , causes header show moment later , therefore "hits" user right in eyes once other content visible.
on top of request every time eventhough 304.
you can use ng-include separate html re-used, can bind data-ng-include variable on scope , change view similar ng-view , using $routeprovider configuration.
i'm not entirely sure attempted reload , seeing not modified response. assume ng-include operate under same caching rules normal page perhaps different since ajax request assume.
Comments
Post a Comment