I have the uploadify control in my app. When running in IE, everything is ok. but when in firefox, it is giving the error:
uploadify flashVer.split is not a function
has anyone experienced this?
I know that this question is quite old, but i had the same issue.
this seems to be a bug with flash that cause it to ignore browser session, instead it pulls cookie from IE no-matter what browser your using, which causes the problem,
since Uploadify uses flash so it wont work in FF or chrome, the bug is not fixed yet, however you might find this URL helpful for some workarounds.
http://joncahill.zero41.com/2009/11/problems-with-uploadify-aspnet-mvc-and.html
Related
I need your help my website is not functioning properly on firefox browser but in edge, chrome and opera and safari it works only firefox is not functioning properly
Firefox Browser
Google Chrome Browser
I would recommend setting up all your projects in Xampp or something similar first before testing it. If you are going to upload to a server you need to replicate the environment locally before you decide whether it is going to work or not. It seems complicated but it is quite simple, you can find out more here. https://www.apachefriends.org/
That said, check your urls, they are not the same for your two different screens, the one is referencing an anchor tag.
I have a very annoying problem with uploadify (2.1.4). My application is working in FF, Chrome, IE9 & 10 but not in IE8. I can see my browse button and I'm able to select all the files I'd like but uploadify won't start uploading the files nor are they shown in the queue.
Now here comes the weird part: whenever I clear my browers history, cookies and temporary internet files, uploadify works fine once. So only once. The second time I try, I get the exact same problem as before.
My QueueId != "queue" so this is not the problem.
I've been trying to find a solution for hours now and I'm about to give up so I hope someone here can help me. I can post my code here if it's needed but I don't know if it would do you any good since everything is working fine except in IE8.
Thanks
Edit: I'm using jquery-1.9.1
I'm hoping someone out there can tell me what's causing the "Continue" button to fail on Firefox with Mac. It's a simple form with a button to select one's country. I'm with a non-profit trying to raise funds for end-of-year giving to help save animals and this page works on "most" browsers: Windows FF, IE, older IE, Chrome, and Mac Safari and Chrome. However, it seems to fail completely on FF on Mac and I don't know why.
The code is all there in the page: www.ifaw.org/united-states/holiday-gift
I'm guessing that the problem is that FF in Mac isn't running the onclick="selectTheRightCountry();" routine. But Javascript is on, so I'm not sure why it doesn't work.
I'm afraid most of my web designing is based on Windows and I'm not a guru in cross-browser Javascript, so I'm not sure what the best way to fix this would be.
Thank you for any help!
This seems to be limited to older versions of Firefox on Mac. Would still be interested to know what caused it if anyone knows, but it's not a huge deal anymore. Thank you!
We have a lot of AJAX in our pages. Mostly it's been in our internal systems, so we haven't tested it with a lot of browsers. But at the moment we're developing a major feature, that will use AJAX, for our customers and we testing it more thoroughly. One of the tests have been in IE9 running IE7 mode, which worked just fine. But when we took a machine running a real IE7 browser, we discovered that AJAX only works once on any of our pages. It seems that after a part of the page is re-rendered with ajax, all javascript events in the part of the HTML that was re-rendered stops working. It's impossible to get even a javascript alert() box to appear.
Since we only have one machine with IE7, we would like to know if anyone can verify that this is a real problem, and not just a problem with this one machine of ours?
And if it is a real problem, what did you do to fix it? 10 % of our users still use IE7, so cutting that browser just isn't a workable solution.
UPDATE / SOLVED:
We decided to get a new server and set it up with Windows XP. Even though we don't support it, we tested it in IE6 and it worked. Then we installed IE7 and it worked too. Guess our old test server is all messed up some how. So all works in IE7 after all.
Thank you for the suggestions all.
Personally I intend to forget about older browsers, but I usually use the jQuery library for my AJAX requests since I usually use jQuery anyway for specific animations etc.
jQuery supports these browsers:
Firefox 3.6, 5.0.x, 6.0.x
Internet Explorer 6+
Safari 5.0.x Opera Current - 1
version Chrome Current - 1 version
source
Because jQuery AJAX is very much part of the jQuery library as anything else, I assume that the jQuery AJAX is supported by these browsers as well.
jQuery AJAX API
AJAX calls are cached in IE. Use "cache: false" in the ajax call options.
I can't seem to work out why my domready function is being called twice.
window.addEvent('domready', function() {
alert('Ready!!111');
}
Its on a joomla 1.6 installation (mootools 1.3) with a joomlart t3 template and a couple of ja modules. Other than that I have my own custom component, nothing special. With a bunch of code that runs when dom is ready. I'v spent many an hour trying to work out why domready is executed twice but to no avail.
Link: http://elwood.visualdomainhosting.com/
Anyone got any ideas on what may be causing this? Or experienced something similar?
Edit:
After some further testing on PC in Firefox, IE, Chrome, Opera and Safari I found the issue is only present on Chrome and Safari. Being a Mac user using both Chrome and Safari for my dev I assumed it was an issues in all browsers (stupid assumption on my part). I'm running Chrome 12.0.742.112 and Safari 5.0.5 (6533.21.1) if you still dont get the same results as I described above.
Looks like the template is using a bunch of Javascript to handle layout functions, not a good practice for just these reasons. I'd consider another template/rework the functionality in PHP.