Filling out form in FedEx Ship Manager is very slow...

Having the same problem in Safari with the Fedex Ship manager. I switched to Firefox on the same machine and the problem did not occur. Thanks to the previous poster that suggested using Firefox, it saved me a lot of time this morning.

As a follow up, it looks like Java update V1.0 2013-005 is NOT the problem. I updated to Safari 6.1 (on Mountain Lion) without this Java update and the problem still occurs.

Having the same problem in Safari with the Fedex Ship manager. I switched to Firefox on the same machine and the problem did not occur. subscribed to thread.😟

As I said already Java is never invoked, so it becomes irrelevant whether you have it installed, or not. The problem is with in the Safari updates 5.1.10 and 6.1 and 7.0. It may, or may not be related to JavaScript handling in those new versions of Safari. It may be something else entirely, but the problem is strictly related to Safari and the fact that it was not apparent in Webkit before the update to the new Safari version, but only after the update suggests, that Apple caries the responsibility for fixing the issue, since it has materialized at the Safari implementation level handled by them, and not by the developers of Webkit.

Same problem here, started happening yesterday. Fedex says their system is a-ok, and not to use Safari when logging in. Apple should fix this.

OK, so another "me too" added to the growing list. Is ANYONE from Apple monitoring this thread who can give us small-medium sized business owners who'd like to use Safari AND FedEx Ship Manager at the same time and kind of ETA on when this will be fixed?

EVERYONE: Best way to get Apple to fix this issue is to have enough users provide feedback. And please be sure make it clear THIS IS VERY OBVIOUSLY A SAFARI PROBLEM, not a FedEx problem, that you know this since the FedEx website works fine with other browsers, and that many other users are also having the same issue (you can provide a link back to this and/or several other posts). Here is the link to leave feedback:

http://www.apple.com/feedback/safari.html

I don't think Apple will pay any attention if we posted feedback. They do what they want and couldn’t care less for the inconveniences of the customers. Didn’t we give you the OS for free??? Besides Mavericks is so full of bugs, as no other OS by Apple to date. I have been participating in other discussions for all the many bugs. Apple has so much work to do, I doubt they know where to begin with. Add to this the old bugs that were never resolved since Lion, like the Finder crashing after multiple drags of attachments in mail for storage to a locally shared drive, or even to folders in the same drive. I don’t want to get started with irrelevant to the subject here issues, but believe me there are MANY bugs that need attention. Now to the current problem, after further testing I concluded that Safari 5.1.10 needs to be excluded from the list of problematic updates. With other words the bug is limited to Safari 6.1 and 7.0 It comes to my mind that they implemented the sandbox per tab, taking the idea from Chrome, so maybe there is a faulty checkup hogging the system. While on Fedex page, the process of the tab crashes and since the other tabs have independent proceses Safari keeps rolling as nothing would have happened and only Finder reports the crash.

Apple does pay attention to feedback in the sense that it indicates the more important from the less important (at least they have in the past). This is why I recommended everyone with the problem leave feedback, and to tell Apple why we know this is their problem (and not a FedEx issue). If you have a better idea (other that the rant) I'm sure others here with this problem will be happy to follow.

I realize this iteration of the OS is discouraging Svetloslav. I should never have upgraded right when it came out and won't err in this manner again anytime soon (at the very least "you get what you pay for" should have overruled what little trust I still had in Apple). For now I'd settle for a browser that doesn't CHOKE when trying to do basic business activities on one of the largest and most used shipping websites out there. But, it would seem you are correct, they are quite unable to discern the important from the unimportant anymore.

Just read where Safari 7.0.1 was seeded to the devs today and Apple asked specifically that they report any "lost functionality" with major websites. Usually takes two or three weeks from this point for a public release.

Maybe a Developer or two ships with FedEx, we can only hope...

I have reported already the bug to the devs. of Webkit some 2 weeks ago and they did not even want to touch the issue. Mind you those same guys usually act upon a bug within 4 to 5 hours after reporting. So it is totally in Apple's court. It is rather sad that I went ahead and grabbed the latest Chromium nightly and had a hard time to distinguish it, since it was working as good as, or even better than Safari before the updates. Common a nightly of google’s browser is better than the official web rendering engine of Apple that ships in their own operating system? That ain’t right!

Ok, so now we have a link to a site completely unrelated to Fedex, which presents the exact same problem as in the Fedex forms. The problem has escalated to a much bigger one. Hopefully Apple wakes up soon, there is plenty of information in their own forums for all the bugs that are plaguing Mavericks. Below the link to the site I talked about.

http://registration.unidistance.ch/registration/

It's something with how Safari is handling the Java on FedEx now

see how there's the new drop down menu on the "to" fields with FedEx? What is happening is that FedEx is trying to prefil suggestions, but Safari is handling the information terribly slow and causing the crash out. You'll have to use the "FedEx Lite" option (without Java) if you want to keep using Safari.

One disappointment after another with Apple lately.

It can be JavaScript related, but is not related to Fedex wanting to inject suggestions from the address book there, because if you go to the form from the link I posted above, you will have the same issue yet the page injects no suggestions, because it knows nothing about the person trying to fill in the form. So the possible culprit is in how an input form object is handled, maybe some JavaScript routines, but I think also the connection with keychain is involved. It must be so, because at the moment you click on the input form element (as seen in Chromium) the program tries to query contacts, or data from your keychain and the address book. Most likely at that point must be the erroneous loop of query, which triggers by clicking on the field and Safari starts running cycles without an actual result and becomes completely unresponsive. So it continues until it gets out of the loop and passes the suggestion. In the next instance the described routine repeats.

you are definitely on the right track - I am experiencing the same issues with phpmyadmin text input fields