title: Placement of the ng-app directive (html vs body)
body: <p>I recently reviewed the code for a webapp built with angular and found that it was written with the <code>ng-app="myModule"</code> directive placed on the <code>&lt;body&gt;</code> tag.  When learning angular, I've only ever seen it used on the <code>&lt;html&gt;</code> tag, as recommended by the angular docs <a href="http://docs.angularjs.org/guide/bootstrap" rel="noreferrer">here</a>, <a href="http://docs.angularjs.org/api/ng.directive:ngApp" rel="noreferrer">here</a>, and in their <a href="http://docs.angularjs.org/tutorial/step_00" rel="noreferrer">tutorial</a>.</p>
  
  <p>I've explored this a bit on my own and found SO questions, notably <a href="https://stackoverflow.com/questions/15583289/multi-modules-in-one-page-with-angularjs">this one</a> and similarly <a href="https://stackoverflow.com/questions/15641730/angular-js-directives-in-different-modules">this one</a>, that discuss loading multiple modules for a page. However, this technique different from my case, as it involves placing ng-app on elements <em>within</em> the body and using manual bootstrapping to run two angular apps at the same time.</p>
  
  <p>As far as I can tell, there is no difference at runtime between an app with <code>ng-app</code> on <code>&lt;html&gt;</code> or <code>&lt;body&gt;</code>.  As I understand it, <code>ng-app</code> designates the root of an angular application, so placement of it on the <code>&lt;body&gt;</code> would cut <code>&lt;head&gt;</code> out of angular's scope, but I can't think of any major way this would affect things.  So my question is: What are the technical difference between placing <code>ng-app</code> on one of these tags instead of the other?</p>