title: How does Angular implement routing internally?
body: <p>In my naive understanding of a web browser, I always thought that if the user enters a new URL into the browser, it would navigate away from the current page, fetch a new page from the network and then display the new page in place of the old page.</p>
  
  <p>However, routing in Angular seems to disprove that naive theory.  If the browser is displaying an Angular page, and the user enter a new URL into the browser, if that URL is controlled by the routing for the Angular application, Angular simply applies its routing, the browser does not access the network, and the page is not replaced.</p>
  
  <p>How does Angular circumvent the normal functioning of the browser in this way?</p>