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

All of a sudden trying to fill out a shipping doc in FedEx Ship Manager is very slow. Each letter typed ends up with athe spinning beach ball for 5 or 6 seconds. Safari version Version 6.1 (8537.71). Never had an Safari issue before with this site and Firefox works fine. (Ended up using FF to get the shipment done)


Any ideas what is going on?

Posted on Oct 24, 2013 10:31 AM

Reply
39 replies

Oct 24, 2013 12:32 PM in response to GTK

MIght be an extension or plugin that was compatible with the previous version of Safari but not 6.1.



Try troubleshooting extensions and third party plugins.


From the Safari menu bar click Safari > Preferences then select the Extensions tab. Turn that OFF, quit and relaunch Safari to test. If that helped, turn one extension on then quit and relaunch Safari to test until you find the incompatible extension then click uninstall.


If it's not an extensions issue, try troubleshooting third party plug-ins.


Back to Safari > Preferences. This time select the Security tab. Deselect: Allow all other plug-ins. Quit and relaunch Safari to test.


If that made a difference, instructions for troubleshooting plugins here.

Nov 14, 2013 8:55 AM in response to nacamera

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

Oct 27, 2013 11:31 AM in response to GTK

Exact same issue here, FedEx shipping page works perfect with other browsers but completely useless in Safari.


This isn't an EXT or Plugin issue (all Apple and and 3rd party have been disabled). Thought it was a Safari 7 problem (just upgraded, but I guess it isn't a version/upgrade issue). Reset Safari, no change, manually deleted everything re Safari & reinstalled fresh, still no change.


If anyone has suggestions (even things they think might work) please post. Would love to quash this LiL bug & post solution for everyone.

Oct 27, 2013 7:18 PM in response to GTK

Makes sense GTK. Updated my Java to "Version 7 Update 45". Anyone know if there are any major consequences to downgrading (asking as I know almost zero about Java, even if it can be done). Tried installing the same update again from the Oracle website. It installed fine, verified fine, but did not solve the problem.


If no one replies or licks this gremlin will do the google thing for info and then backup so I can give an older version a go.

Oct 28, 2013 3:09 AM in response to GTK

I have the same problem with an other website. Filling the text fields of one often used form is very slow. Safari 5.1 and Chrome ist fast. In Safari 7.0 the entered text shows up letter by letter. Deactivating CSS and JS did not help. Reseting Safari did not help. I thought of a problem with autofilling, but deactivating form filling made no change either.


Java is not installed.

Oct 29, 2013 5:04 PM in response to GTK

Same problem here. Just started with a recent update to Safari 6.1. No extensions are installed.


However, I noticed that the slow down to unusable seems to only happen on the "Create Shipment" page. When I type into text fields on the "Get Rates & Transit Times" page, the response is immediate, as fast as it's always been. No beachballs at all.


Perhaps when on the Create Shipment page, the data travels as encrypted in some new way that FedEx is having an issue with. Note the little lock icons on the Ship tab pull down menu in Ship Manager. The Create Shipment selection has one, while Get Rates & Transit Times doesn't.

Oct 31, 2013 2:05 PM in response to GTK

Same here, I create many, many Fedex labels on a daily basis for work. In Mountin Lion things were working excellent, just upgraded to Mavericks and Fedex is unusable. Firefox (even in its latest version 25) works perfect with Fedex and on Mavericks too. This is definitely a problem caused by Mavericks and has nothing to do with FedEx. I think it is related to how security for JavaScript has been changed, or how Sandboxing in tabs and JavaScript relate to each other in the new version of Safari. No updates to the latest Java will fix it, because the fields on the FedEx form are populated through JavsScript coding and in this case Java is not being invoked at all. Thats why you may have different versions of Java installed, or not even have it installed, yet in Safari 7.0 those forms from FedEx and evidently form some other sites will beachball. So the only solution currently is to use another browser, which is really a lame solution. If Apple wants to make us use Safari more often, step up to the plate and show an improvement in the browser, not regressions. Mind you this is a huge regression! I have been creating labels in Fedex for some 7-8 years now and there has never been an update to Safari that would cause such a disaster. And by the way, I use Webkit nightlies. Granted the developers there tend to break things, but are very responsive and provide a fix usually within day or two. Those are the same guys that develop the new versions of Safari core and rendering, so I'm curious as to who would be voicing support here in the discussion. One thing is clear, even todays nightly of Webkit is also beachballing, so the problem is not directly related to Webkit.

Oct 31, 2013 6:05 PM in response to GTK

Just tested with today's Chromium nightly (stay away from the official Chrome full of google spyware and system hoggers). With Chromium FedEx works flawlessly. So as a conclusion to the previous posts, the problem is not related to the OS itself (Mavericks, or Mountain Lion), but both Safari 6.1 and 7.0 are to be blamed for. Common Apple, we did the beta testing for you, now is your turn to move fast!

Nov 8, 2013 6:45 AM in response to Stephen Presta

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.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.