Can someone help me here?
I cannot understand why ONLY in iOS the "Autenticar" button does not work! :(
http://www.select.pt.la/
It works on "ALL" browsers in Windows and Android, but in iOS... nothing!
Can't figure this out.
EDIT:
Since this is a test platform, you can login with
User: demo
Pass: demo
You have some serious issues on that site which could be having all kinds of strange effects. You are running javascripts that need jquery, and jquery is not loaded
Why not use this free plugin to see if it stops the errors, and as a secondary function fixes your button
JQuery Easy
Related
After having deployed my gatsby website with netlify, I realised that while it seems to work perfectly on other browsers, JavaScript seems to be disabled for the site on Firefox and google fonts does not seem to have worked as well. Anyone know why this could be? Highly appreciate any help!
Site for Reference
I had a regex with a lookbehind, so firefox disabled my JavaScript.
I am under the (perhaps mistaken?) impression that you can test jQuery Mobile applications during development using Safari rather than having to use a mobile device.
When I
load Safari in Windows,
change the User Agent to Safari iOS 4.3.3 — iPhone in the Developer menu,
hit this URL: http://jquerymobile.com/test/docs/forms/forms-sample.html, and
click Submit on the Default Ajax form example
it does not AJAX. Instead it loads a new URL:
http://jquerymobile.com/test/docs/forms/forms-sample-response.php?shipping=Standard+shipping&submit=submit-value
Are my expectations wrong, am I doing it wrong, or is there something wrong with jQuery Mobile?
I don't think anything is wrong, I think you're just being fooled by jQuery Mobile.
It may appear as though a whole-page-refresh is occuring but it isn't. If you watch the Network tab in your developer tools you can see the XHR request for the PHP page.
Then jquery Mobile is changing the URL in the address bar with it's pushState plugin: http://jquerymobile.com/test/docs/pages/page-navmodel.html
In a general sense, yes, you can use a desktop browser for development but be ready for issues when you move to testing on a device. Sometimes you don't get any, but there are some frustrating bugs in the current mobile browsers.
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.
http://www.myprettyvintage.com is having an issue with the twitter widget in the sidebar.
It works fine in all browsers except for Firefox. I think its a CSS issue but right now I'm clutching at straws any help would be appreciated.
I had this same problem, and I narrowed it down to cookies possibly being blocked. I was running an Add-On called 'Disconnect' from https://disconnect.me/ . Once I disabled this addon and restarted the browser! the twitter widget started working again.
So if you're using that addon or any other one to block cookies or prevent you from being tracked by social networking sites, you'll need to disable it if you want to see the twitter widget.
For me it was the AddBlocker in Firefox....disable it for your site and reload the site to test it.
Insert a
div.twtr-doc{margin-top: 37px;}
to your css file. I had the same thing. took me a week to figure this one out.
Options --> Privacy --> Uncheck "Use Tracking Protection In Private Windows"
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.