title: Preserve traditional anchor behavior with ng-include
body: <p>I am not building a single-page application, but rather a "traditional" site that uses AngularJS in places. I've hit the following problem (using 1.3.0-beta.6):</p>
  
  <p>Standard, working anchor links:</p>
  
  <pre><code>&lt;a href="#foo"&gt;Link text&lt;/a&gt;
  ... [page content]
  &lt;a id="foo"&gt;&lt;/a&gt;
  &lt;h1&gt;Headline&lt;/h1&gt;
  [more content]
  </code></pre>
  
  <p>That works fine. Now I introduce a template partial somewhere:</p>
  
  <pre><code>&lt;script type="text/ng-template" id="test-include.html"&gt;
    &lt;p&gt;This text is in a separate partial and inlcuded via ng-include.&lt;/p&gt;
  &lt;/script&gt;
  </code></pre>
  
  <p>which is invoked via:</p>
  
  <pre><code>&lt;div ng-include="'test-include.html'"&gt;&lt;/div&gt;
  </code></pre>
  
  <p>The partial is included properly, but the anchor link no longer works. Clicking on "Link text" now changes the displayed URL to <code>/#/foo</code> rather than <code>/#foo</code> and the page position does not change. </p>
  
  <p>My understanding is that using <code>ng-include</code> implicitly tells Angular that I want to use the routes system and overrides the browser's native anchor link behavior. I've seen recommendations to work around this by changing my html anchor links to <code>#/#foo</code>, but I can't do that for other reasons.  </p>
  
  <p>I don't intend to use the routes system - I just want to use <code>ng-include</code> without it messing with browser behavior. Is this possible?</p>