[jQuery] Re: JQuery on Safari 3.1.2 Windows
You just need to validate your html. Your close anchor needs to be /a not
a and your div class needs a closing quote.
- Richard
On Fri, Nov 14, 2008 at 3:23 PM, cman [EMAIL PROTECTED] wrote:
Hello all,
I'm having an issue with JQuery and Safari (Windows Version). The
code works on FF/IE7/Chrome but not Safari.
I have a simple li that has a div embedded in to - clicking the
li should expose the hidden div, but not in Safari.
The HTML:
ul
lisomething/li
lisomething2/li
li class=more
a class=moreFacetsLinkClick to see more optionsa
div class=moreFacetsbunch of text/div
/li
/ul
Here is the JQuery code:
$('.moreFacetsLink').click(function () {
$(this).siblings('div').toggle();
});
Any thoughts as to what may be going on here?
I'm a newbie when it comes to JQuery.
Thanks!
[jQuery] Re: jquery and safari
I think I did this to enable it... http://www.macosxhints.com/article.php?story=2007061303320554 On Jan 2, 10:31 am, Alexandre Plennevaux [EMAIL PROTECTED] wrote: hiYabado, can you tell me more about it? i found the script console log in safari, but it doesn't show any error. but i do not see the inspect element command . Where is it to be found? thanks a lot alex On Jan 2, 2008 12:21 PM,yabado[EMAIL PROTECTED] wrote: Have you tried the new Inspect Element contextual command? It will show any errors in the console for you. On Dec 31 2007, 7:09am, pixeline [EMAIL PROTECTED] wrote: hi! i'm having issues to have my project work in safari. No problem with Firefox, IE6+ or Opera, just Safari, both the mac and windows versions. The symptom is: the page is empty! only the background image shows, and nothing on top! My code is quite long so instead of burdening you under it, i would rather ask an open question about any known issues with Safari and jquery? thanks for your help! Alexandre -- Alexandre Plennevaux LAb[au] http://www.lab-au.com
[jQuery] Re: jquery and safari
Have you tried the new Inspect Element contextual command? It will show any errors in the console for you. On Dec 31 2007, 7:09 am, pixeline [EMAIL PROTECTED] wrote: hi! i'm having issues to have my project work in safari. No problem with Firefox, IE6+ or Opera, just Safari, both the mac and windows versions. The symptom is: the page is empty! only the background image shows, and nothing on top! My code is quite long so instead of burdening you under it, i would rather ask an open question about any known issues with Safari and jquery? thanks for your help! Alexandre
[jQuery] Re: jquery and safari
hi Yabado, can you tell me more about it? i found the script console log in safari, but it doesn't show any error. but i do not see the inspect element command . Where is it to be found? thanks a lot alex On Jan 2, 2008 12:21 PM, yabado [EMAIL PROTECTED] wrote: Have you tried the new Inspect Element contextual command? It will show any errors in the console for you. On Dec 31 2007, 7:09am, pixeline [EMAIL PROTECTED] wrote: hi! i'm having issues to have my project work in safari. No problem with Firefox, IE6+ or Opera, just Safari, both the mac and windows versions. The symptom is: the page is empty! only the background image shows, and nothing on top! My code is quite long so instead of burdening you under it, i would rather ask an open question about any known issues with Safari and jquery? thanks for your help! Alexandre -- Alexandre Plennevaux LAb[au] http://www.lab-au.com
[jQuery] Re: jquery and safari
My code is quite long so instead of burdening you under it, i would rather ask an open question about any known issues with Safari and jquery? Don't know of any known issues, other than the many I've encountered personally. Which version are you running on Mac? The 3.0 beta on Tiger gave me a lot of problems, but they seem to have mostly settled with the full 3.0 that shipped with Leopard... only thing I can suggest is try to break down the code, see if you can identify what specifically is causing the script to fail.
[jQuery] Re: Jquery and safari
I'm using Safari 2 up to yesterday, jquery works well in my case, I just upgraded to 3.0 hoping the file uploading problem in Safari will go away(it does not), all the javascript still working. care to send a sample for me to test it out? On Oct 24, 3:05 pm, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I am running safari 2.0.4 and jquery 1.2.1. None, and I mean none of my javascript works in safari. All of it works fine in firefox and most of it works in ie. Is this just a problem with jquery or am I missing something?
[jQuery] Re: Jquery and safari
Can you post your jquery code? I had the same problem and it appeared to be wrongly defined functions. On 24 okt, 09:05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I am running safari 2.0.4 and jquery 1.2.1. None, and I mean none of my javascript works in safari. All of it works fine in firefox and most of it works in ie. Is this just a problem with jquery or am I missing something?
[jQuery] Re: Jquery and safari
[EMAIL PROTECTED] wrote: I am running safari 2.0.4 and jquery 1.2.1. None, and I mean none of my javascript works in safari. All of it works fine in firefox and most of it works in ie. Is this just a problem with jquery or am I missing something? Safari is pants :)
[jQuery] Re: Jquery and safari
I think there must be something specific in your project. If you have something online that could be reviewed it would be helpful. Personally, I'm developing an application which has been successfully tested in IE6, IE7, FF, Opera and Safari 2, so I know that it does work. JK _ From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Guy Fraser Sent: Wednesday, October 24, 2007 6:12 AM To: jquery-en@googlegroups.com Subject: [jQuery] Re: Jquery and safari [EMAIL PROTECTED] wrote: I am running safari 2.0.4 and jquery 1.2.1. None, and I mean none of my javascript works in safari. All of it works fine in firefox and most of it works in ie. Is this just a problem with jquery or am I missing something? Safari is pants :)
[jQuery] Re: Jquery and safari
_uacct = UA-1454666-2;
$(document).ready(function(){
urchinTracker();
$('.admin .body').each(function(){ $(this).hide();});
$('.more').click(adminBodyToggle);
$('#content').corner('15px');
$(.delete).click(ajaxDelete);
$(.update).click(ajaxUpdate);
$('.page_add').click(function(){ newForm(form.remote); return
false;});
//$('.file_add').click(function(){ newForm(form.file_remote);
return false;});
$('form.remote .cancel').click(function(){ newForm(form.remote);
return false;});
//$('form.file_remote .cancel').click(function()
{ newForm(form.file_remote); return false;});
$(form.remote).ajaxForm({
dataType: 'script',
beforeSend: function(xhr) {
$(form.remote).prepend('div class=flash
warningSending
data.../div');
xhr.setRequestHeader(Accept, text/javascript);},
});
$(input.autocomplete).each(function(){
var id = this.id;
$.ajax({
url: /autocomplete/+id,
dataType: json,
success: function(msg) {
$([EMAIL
PROTECTED]+id+\]).autocompleteArray(msg);
}
})
});
$(.popup_cal).each(function(){ $(this).calendar();});
$(.wymeditor).each(function(){ $(this).wymeditor();});
});
That's the bulk of it. I am using the corners plugin and form plugin
on all pages. Then the wymeditor, ui calendar and autocomplete on some
pages. Even just a on page where I have a link return false and show a
hidden div breaks and goes to the default url (which I put in there
for graceful degradation).
On Oct 24, 8:11 am, Guy Fraser [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
I am running safari 2.0.4 and jquery 1.2.1. None, and I mean none of
my javascript works in safari. All of it works fine in firefox and
most of it works in ie. Is this just a problem with jquery or am I
missing something?
Safari is pants :)
[jQuery] Re: Jquery and safari
I'm sort of reaching here as I don't have access to your completed page to
test on, but perhaps the urchinTracker method is throwing an error?
One of the annoying things about Safari 2 is that when an error is
encountered all javascript on the page halts completely with no message or
notification.
I would remove all of your commands but one, see if it executes, then add
each in one at a time to find the offending line.
Start with this only:
$(document).ready(function(){
$('.admin .body').hide();
});
See if it works. Then add one new command at a time testing between each
one. Add the urchinTracker command last.
JK
-Original Message-
From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, October 24, 2007 10:13 AM
To: jQuery (English)
Subject: [jQuery] Re: Jquery and safari
_uacct = UA-1454666-2;
$(document).ready(function(){
urchinTracker();
$('.admin .body').each(function(){ $(this).hide();});
$('.more').click(adminBodyToggle);
$('#content').corner('15px');
$(.delete).click(ajaxDelete);
$(.update).click(ajaxUpdate);
$('.page_add').click(function(){ newForm(form.remote); return
false;});
//$('.file_add').click(function(){ newForm(form.file_remote);
return false;});
$('form.remote .cancel').click(function(){ newForm(form.remote);
return false;});
//$('form.file_remote .cancel').click(function()
{ newForm(form.file_remote); return false;});
$(form.remote).ajaxForm({
dataType: 'script',
beforeSend: function(xhr) {
$(form.remote).prepend('div class=flash
warningSending
data.../div');
xhr.setRequestHeader(Accept, text/javascript);},
});
$(input.autocomplete).each(function(){
var id = this.id;
$.ajax({
url: /autocomplete/+id,
dataType: json,
success: function(msg) {
$([EMAIL PROTECTED]+id+\]).autocompleteArray(msg);
}
})
});
$(.popup_cal).each(function(){ $(this).calendar();});
$(.wymeditor).each(function(){ $(this).wymeditor();});
});
That's the bulk of it. I am using the corners plugin and form plugin
on all pages. Then the wymeditor, ui calendar and autocomplete on some
pages. Even just a on page where I have a link return false and show a
hidden div breaks and goes to the default url (which I put in there
for graceful degradation).
On Oct 24, 8:11 am, Guy Fraser [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
I am running safari 2.0.4 and jquery 1.2.1. None, and I mean none of
my javascript works in safari. All of it works fine in firefox and
most of it works in ie. Is this just a problem with jquery or am I
missing something?
Safari is pants :)
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
Anyone know when 1.1.1.4 is going to be released? On Aug 14, 4:12 pm, Ken [EMAIL PROTECTED] wrote: I know you, and the other developers, are probably very busy with life and everything, but I was curious if there was any word on the new version of jQuery. I am highly interested in fixes for this Safari problem. :) Also, thank you to John and everybody else for all of the hard work and genius being put into jQuery. - Ken On Aug 7, 8:53 am, John Resig [EMAIL PROTECTED] wrote: This bug was found just after the 1.1.3.1 release - a ticket was opened on it and a new version was provided to those that were effected. The fix will be included in the upcoming 1.1.4 release (which should be coming out today or tomorrow). --John
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
1.1.4 will probably be released tonight, if I can resolve some of these final, sticky, bugs. --John On 8/20/07, ru [EMAIL PROTECTED] wrote: Anyone know when 1.1.1.4 is going to be released? On Aug 14, 4:12 pm, Ken [EMAIL PROTECTED] wrote: I know you, and the other developers, are probably very busy with life and everything, but I was curious if there was any word on the new version of jQuery. I am highly interested in fixes for this Safari problem. :) Also, thank you to John and everybody else for all of the hard work and genius being put into jQuery. - Ken On Aug 7, 8:53 am, John Resig [EMAIL PROTECTED] wrote: This bug was found just after the 1.1.3.1 release - a ticket was opened on it and a new version was provided to those that were effected. The fix will be included in the upcoming 1.1.4 release (which should be coming out today or tomorrow). --John
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
That is awesome! Thank you very much, and I will keep my fingers crossed for you. :) On Aug 20, 11:18 am, John Resig [EMAIL PROTECTED] wrote: 1.1.4 will probably be released tonight, if I can resolve some of these final, sticky, bugs. --John On 8/20/07, ru [EMAIL PROTECTED] wrote: Anyone know when 1.1.1.4 is going to be released? On Aug 14, 4:12 pm, Ken [EMAIL PROTECTED] wrote: I know you, and the other developers, are probably very busy with life and everything, but I was curious if there was any word on the new version of jQuery. I am highly interested in fixes for this Safari problem. :) Also, thank you to John and everybody else for all of the hard work and genius being put into jQuery. - Ken On Aug 7, 8:53 am, John Resig [EMAIL PROTECTED] wrote: This bug was found just after the 1.1.3.1 release - a ticket was opened on it and a new version was provided to those that were effected. The fix will be included in the upcoming 1.1.4 release (which should be coming out today or tomorrow). --John
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
I know you, and the other developers, are probably very busy with life and everything, but I was curious if there was any word on the new version of jQuery. I am highly interested in fixes for this Safari problem. :) Also, thank you to John and everybody else for all of the hard work and genius being put into jQuery. - Ken On Aug 7, 8:53 am, John Resig [EMAIL PROTECTED] wrote: This bug was found just after the 1.1.3.1 release - a ticket was opened on it and a new version was provided to those that were effected. The fix will be included in the upcoming 1.1.4 release (which should be coming out today or tomorrow). --John
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
So, for my solution, I have a conditional that uses jQuery 1.1.3.1 for Safari with version numbers 417 and higher, and jQuery 1.1.2 for Safari versions between 312 and 416. How do you do that? If your code works with 1.1.2, why not use it and forget 1.1.3.1 until it's fixed? If the problem is with those older versions of Safari, they will never be fixed. Conditional includes are handled in ColdFusion using cfif tags and browser detection code. Reverting to jQuery 1.1.2 for the entire site was an option I considered. I am under the impression that 1.1.3 is better than 1.1.2, unless you are using one of the browsers that crashes. I decided I didn't want to hold back progress that benefits the majority of users due to a small number of people running old software. I noticed that the official browser requirements are more strict than what I have in my notes from a while back. I have in old code comments that jQuery works with Safari 1.3, Firefox 1.0, MSIE 5.5, and Opera 8.5, but the Web site now lists Safari 2, Firefox 1.5, MSIE 6, and Opera 9. -Mike Chabot
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
On Aug 7, 2007, at 7:55 AM, Mike Chabot wrote: script src=jquery-1.1.3.1.pack.js type=text/javascript/script Is it happening with packed version only? -- Mika Tuupola http://www.appelsiini.net/~tuupola/
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
The website does report opera 9.x as a requirement, but so far I've found nothing that doesn't work in Opera 8.x except for transparency effects, and they fail gracefully without causing any browser crashes, so I'd say the documentation is a little strict regardign compatibility. As long as you don't use opacity or use it in a non- obtrusive way then everything still works in 8.x Regarding your specific problem, have you tried running the uncompressed version of jQuery in place of the compressed version? While it wouldn't be sensible to deploy it on a live site for obvious reasons, using the uncompressed versions for testing has huge benefits for debugging as it's a lot easier to determine where a failure occured. On Aug 7, 7:08 am, Mike Chabot [EMAIL PROTECTED] wrote: So, for my solution, I have a conditional that uses jQuery 1.1.3.1 for Safari with version numbers 417 and higher, and jQuery 1.1.2 for Safari versions between 312 and 416. How do you do that? If your code works with 1.1.2, why not use it and forget 1.1.3.1 until it's fixed? If the problem is with those older versions of Safari, they will never be fixed. Conditional includes are handled in ColdFusion using cfif tags and browser detection code. Reverting to jQuery 1.1.2 for the entire site was an option I considered. I am under the impression that 1.1.3 is better than 1.1.2, unless you are using one of the browsers that crashes. I decided I didn't want to hold back progress that benefits the majority of users due to a small number of people running old software. I noticed that the official browser requirements are more strict than what I have in my notes from a while back. I have in old code comments that jQuery works with Safari 1.3, Firefox 1.0, MSIE 5.5, and Opera 8.5, but the Web site now lists Safari 2, Firefox 1.5, MSIE 6, and Opera 9. -Mike Chabot
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
Is it happening with packed version only? From Mike Chabot's original email: I performed my tests with both the packed version and the unpacked version. The packed version caused the browser to crash more quickly. With the unpacked version, I sometimes had to refresh the browser window a couple times before the crash occurred. --Erik
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
Regarding your specific problem, have you tried running the uncompressed version of jQuery in place of the compressed version? While it wouldn't be sensible to deploy it on a live site for obvious reasons, using the uncompressed versions for testing has huge benefits for debugging as it's a lot easier to determine where a failure occured. Live sites should be running GZIP to compress static files--so there's no reason some should be running the pack version. I usually avoid running packed code because there's some inherited overhead while it unpacks. Also, running packed code makes it extremely difficult to troubleshoot if users are reporting problems. -Dan
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
This bug was found just after the 1.1.3.1 release - a ticket was opened on it and a new version was provided to those that were effected. The fix will be included in the upcoming 1.1.4 release (which should be coming out today or tomorrow). --John On 8/7/07, Mike Chabot [EMAIL PROTECTED] wrote: jQuery 1.1.3.1 Safari Crashes After upgrading a high-traffic Web site from jQuery 1.1.2 to jQuery 1.1.3.1, some Safari users started reporting that the Web site would cause their browsers to crash. The crash would be that Safari would instantly shut down. I set up multiple test environments using clean installs of Mac OS 10.4.0 through Mac OS 10.4.4 (with some newer 10.4.10 systems already in place), to determine which versions of Safari experienced this problem. This is the basic test code: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN htmlheadtitle/title script src=jquery-1.1.3.1.pack.js type=text/javascript/script /headbody/body/html There is zero functionality in that test code. It is just an include of the jQuery file. After loading this simple page, Safari 2.0.0 (412) through 2.0.2 (416.12) immediately crash. The error is 100% reproducible. Safari 2.0.3 (417.8) works. Safari 2.0.3 and 2.0.4 passed all of my more complex tests, which simulate the complex functionality found in the Web site. Based on user reports, I suspect that jQuery 1.1.3.1 would also cause versions of Safari older than 2.0 to crash. One person using Safari 1.3 reported a crash. I did not try to reproduce this. I performed my tests with both the packed version and the unpacked version. The packed version caused the browser to crash more quickly. With the unpacked version, I sometimes had to refresh the browser window a couple times before the crash occurred. jQuery 1.1.2 seems to work fine in these older versions of Safari. It passed all the complex tests, not simply the crash-avoidance test. So, for my solution, I have a conditional that uses jQuery 1.1.3.1 for Safari with version numbers 417 and higher, and jQuery 1.1.2 for Safari versions between 312 and 416. I hope this helps, Mike Chabot
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
On Aug 7, 2007, at 3:48 PM, Dan G. Switzer, II wrote: Live sites should be running GZIP to compress static files--so there's no reason some should be running the pack version. Agreed. Minified gzipped javascript is my choice. -- Mika Tuupola http://www.appelsiini.net/~tuupola/
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
I tested using the unpacked version as well as the packed version and the problem exists in both. Unfortunately, there is no error message identifying a line number, since the symptom is that Safari immediately shuts down. A window with crash details pops up, asking me to send the info to Apple. The error details didn't point to a problem that a Web developer can easily address. It was some memory error related to JavaScript, if I remember correctly. -Mike Chabot On 8/7/07, Gordon [EMAIL PROTECTED] wrote: Regarding your specific problem, have you tried running the uncompressed version of jQuery in place of the compressed version? While it wouldn't be sensible to deploy it on a live site for obvious reasons, using the uncompressed versions for testing has huge benefits for debugging as it's a lot easier to determine where a failure occured.
[jQuery] Re: jQuery 1.1.3.1 Safari Crashes
On Aug 7, 2:55 pm, Mike Chabot [EMAIL PROTECTED] wrote: jQuery 1.1.3.1 Safari Crashes After upgrading a high-traffic Web site from jQuery 1.1.2 to jQuery 1.1.3.1, some Safari users started reporting that the Web site would cause their browsers to crash. The crash would be that Safari would instantly shut down. I set up multiple test environments using clean installs of Mac OS 10.4.0 through Mac OS 10.4.4 (with some newer 10.4.10 systems already in place), to determine which versions of Safari experienced this problem. This is the basic test code: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN htmlheadtitle/title script src=jquery-1.1.3.1.pack.js type=text/javascript/script /headbody/body/html There is zero functionality in that test code. It is just an include of the jQuery file. After loading this simple page, Safari 2.0.0 (412) through 2.0.2 (416.12) immediately crash. The error is 100% reproducible. Safari 2.0.3 (417.8) works. Safari 2.0.3 and 2.0.4 passed all of my more complex tests, which simulate the complex functionality found in the Web site. Ouch... Based on user reports, I suspect that jQuery 1.1.3.1 would also cause versions of Safari older than 2.0 to crash. One person using Safari 1.3 reported a crash. I did not try to reproduce this. I performed my tests with both the packed version and the unpacked version. The packed version caused the browser to crash more quickly. With the unpacked version, I sometimes had to refresh the browser window a couple times before the crash occurred. jQuery 1.1.2 seems to work fine in these older versions of Safari. It passed all the complex tests, not simply the crash-avoidance test. Thanks for the heads-up. :-) So, for my solution, I have a conditional that uses jQuery 1.1.3.1 for Safari with version numbers 417 and higher, and jQuery 1.1.2 for Safari versions between 312 and 416. How do you do that? If your code works with 1.1.2, why not use it and forget 1.1.3.1 until it's fixed? If the problem is with those older versions of Safari, they will never be fixed. -- Rob
