-
Notifications
You must be signed in to change notification settings - Fork 27.4k
IE8 9: a link route error(angular 1.2.17 1.2.18) #7892
Comments
+1 |
1 similar comment
+1 |
Can you confirm that this wasn't an issue in 1.2.17? Also, a plunkr that reproduces the problem would help a lot |
@rodyhaddad this is a confirmed issue, although it hasn't been narrowed down to a specific commit. It was most likely my changes which were supposed to make relative route resolution work better in legacy browsers. It's hard to sort out where the problem started happening, because I do remember this working when those were checked in, but without a legacy IE browser to use, it's a bit hard to sort out. |
Hi @rodyhaddad Yeah that issue was introduced on 1.2.17 also exist in 1.2.18 and 1.3 beta 13 I already opened another ticket #7892 (comment) where you may find the repro for this issue, however you repro this just going to the route doc page and try to use the demo in there |
i think this is the issue i created at #8172 too. |
This should also be fixed by #8492 --- but I'm moving it to the next milestone in case the revert doesn't land today |
Can it put to 1.2.x version as well? |
@winsontam +1 |
Hi, Press the links and then look into the browser console. Closing this, please comment if you have a plunker/jsfiddle to reproduce this. |
Ah, IE9 does not open plunker. |
@acostaf Your link points to this same issue. Do you still have the reproduction case? |
@tbosch this is still broken and this may be the easiest bug to reproduce, open https://docs.angularjs.org/#!/api/ngRoute/service/$route on IE9 then try to run the sample at the end of the page pressing the books button. |
@tbosch yes It does |
if my angular version is 1.2.18
base element, href is '/n/b/'
my a link's href is 'c/xx'
so i click this link then
if the current location.href is 'http://www.x.com/n/b/#!/'
if the current location.href is 'http://www.x.com/n/b/#!/c/yy'
Please check it.
The text was updated successfully, but these errors were encountered: