DanWahlin / Angular-JumpStart

Angular and TypeScript JumpStart example application

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

View All Customers Link from Orders page returns no results

ckapilla opened this issue · comments

(first of all thank you for creating the most sophisticated A2 starter I've seen)
View All Customers link on the Orders page has two issues:

  1. ) it seems to require a double-click
    2.) The Customer Manager page then always returns 'No Records Found' in List View (it seems that neither view is actually selected at this point). Then clicking on either Card View or List View will populate the data.

Thanks! Glad to hear the project has been useful to you.

I just tried things out and aren't seeing the issues you mention. Can you let me know what browser you were trying it in?

Oh, you are correct -- the problem isn't occurring in Chrome or FF. I'm seeing it in Edge. Another part of the issue in Edge is that you need to double-click on 'View All Customers' before it goes to the next page. I don't think this is worth your time to fix at this point.

Good to know - thanks. I don't have a fix for that at this point but will pass the info along to the Angular team. If I find out anything I'll update the thread.

Thank's for this sample, very helpful.

Great example, thanks!

Thanks - glad to hear it's helpful.

Interesting - not working in IE(11)

SCRIPT438: Object doesn't support property or method 'keys'

On Fri, Jan 22, 2016 at 2:19 PM, Dan Wahlin notifications@github.com
wrote:

Thanks - glad to hear it's helpful.


Reply to this email directly or view it on GitHub
#14 (comment)
.

I'm seeing an error in IE11 (on Windows 10) as well although my error is related to RouteConfig. Not sure what might be causing that since it's working in other browsers so I suspect it may be a framework issue with that specific browser. I don't have time to dig in more right now but if you happen to find anything let me know.

Incidentally, it seems to be working fine for me in Edge though now @ckapilla. I haven't made any changes that should affect that so I'm not sure what may have changed there aside from a Windows update.

As a heads-up, I was just informed that the way the polyfills load (for IE) has changed from what we've been doing for quite awhile. You can read the very bottom of the routing docs here for more info.

https://angular.io/docs/ts/latest/guide/router.html#!#browser-url-styles

I updated the app just now to the polyfill order shown in the docs but still have a problem in IE11 unfortunately. Edge seems to be working great though. Just wanted to point out the polyfill change in case you hadn't seen it yet (it was news to me :-)).