Did you know that main AngularJS.org page is not accessible with IE9?

[crussi]

I was testing my AngularJS app with IE9. I noticed that I could not navigate to the main AngularJS.org website home page: http://angularjs.org/#/list in IE9.

It seems to be stuck in an infinite routing loop. Going from http://angularjs.org to http://angularjs.org/#/list to http://angularjs.org to http://angularjs.org/#/list.

I just thought I would mention it because AngularJS is incredibly important new advancement in browser apps :-)

Best regards,
Chris

[IgorMinar]

We are looking into the issue

[crussi]

Thank you kindly for all your efforts. The AngularJS framework is an
incredible thing. I just happened to be testing my app in IE and noticed
this issue. I just want to say I am thankful for all that has been done to
make AngularJS so awesome.

Best regards,
Chris Russi

On Thu, Jun 21, 2012 at 4:21 PM, Igor Minar <
reply@reply.github.com

wrote:

We are looking into the issue

---

Reply to this email directly or view it on GitHub:
#1075 (comment)

[nikyoudale]

We've been using Angular for several months now and it's been awesome :)

Here's a workaround we're using for this issue (forces a refresh from any url like example.com/app/foo/bar to example.com/app/#/foo/bar, assuming that there is a <base href="/app/"> tag):

<script type="text/javascript">
  if (window.history == undefined || window.history.pushState == undefined) {
    if (!window.location.hash) {
      var baseHref = document.getElementsByTagName('base')[0].href;
      baseHref = baseHref ? baseHref.replace(/^https?\:\/\/[^\/]*/, '') : baseHref;

      var matches = window.location.pathname.match(new RegExp("^"+baseHref+"(.*)$"));
      var thePath = matches && matches.length > 1 ? matches[1] : "";

      window.location = baseHref+"#/"+thePath;
    }
  }
  </script>

[IgorMinar]

should be fixed on the site now. the fix will be included with 1.0.1

[crussi]

Awesome!

Sent from my iPad

On Jun 22, 2012, at 12:42 PM, Igor Minarreply@reply.github.com wrote:

should be fixed on the site now. the fix will be included with 1.0.1

---

Reply to this email directly or view it on GitHub:
#1075 (comment)