subject:"Re\: \[jQuery\] Is it a bug"

Re: [jQuery] IE bug or bug in my code ?

2007-03-20 Thread Remy Sharp


Hi Jack,

Occasionally I get the oddity of JavaScript not working in IE too, so I
recently converted the 
http://remysharp.com/2007/03/13/firebug-in-ie-for-any-web-site/ Firebug lite
to a bookmarklet  so you can easily debug what's going on any page.

I would recommend adding a few console.info and console.dir (to dump
objects) within your code to see what's going on inside IE.


Jack Gleeson wrote:
 
 But in IE the above code does not work, I thought it would be an issue
 with using swfobject with jquery buty I patched that up and the issue
 is still unsolved.
 
 It's pretty simple code, it hides 4 forms on load and then whatever
 option you select from the select list, it shows the form. It works
 fine in Firefox but in IE when I submit the page and do my regular
 expression checks it shows all forms which is not correct.
 

-- 
View this message in context: 
http://www.nabble.com/IE-bug-or-bug-in-my-code---tf3432817.html#a9576217
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] IE bug or bug in my code ?

2007-03-20 Thread Jack Killpatrick

FWIW, I've had issues in IE 6/7 with $(document).ready() not firing 
something in it's function. I've never dug into exactly why it happens, 
but found a workaround using setTimeout, like this:

$(document).ready(function() {
setTimeout(
function(){
   your code that isn't firing in IE here
}
, ( $.browser.msie ) ? 500 : 0
)
});

So, maybe give that a try. FWIW, we (me and the folks I work with) found 
that 500ms seemed to do the trick, but 100ms didn't.

Also, If anyone knows why that's needed for some things to fire via 
$(document).ready, I'd love to know. We've also worked around it by 
doing these things:

1. putting our $(document).ready at the end of the HTML page (after the 
objects that we need ready).
2. used setTimeout() to check for the presence of the object(s) we need 
ready, and when they become ready, binding to them.

- Jack

Jack Gleeson wrote:
 In firefox the follow code works fine

  $(document).ready(function() {
  $(.form_con).hide();
  $([EMAIL PROTECTED]).change( function() {
  if($.browser.safari) {
  if(this.value != 0)
  $(.form_con).hide();
  $(#form + (this.value)).show();
  } else {
  if(this.value != 0) {
  $(.form_con).hide();
  $(#form + (this.value)).fadeIn(slow);
  }
  }
  });
 });

 But in IE the above code does not work, I thought it would be an issue
 with using swfobject with jquery buty I patched that up and the issue
 is still unsolved.

 It's pretty simple code, it hides 4 forms on load and then whatever
 option you select from the select list, it shows the form. It works
 fine in Firefox but in IE when I submit the page and do my regular
 expression checks it shows all forms which is not correct.

 Here is the on submit code,

 $(document).ready(function() {
  $(.form).hide();
  $(#form + (?php echo $contype; ?)).show();
  $('#conveyancing_list').attr('disabled', 'disabled');
  $([EMAIL PROTECTED]).change( function() {
  if($.browser.safari) {
  if(this.value != 0)
  $(.form).hide();
  $(#form + (this.value)).show();
  } else {
  if(this.value != 0) {
  $(.form).hide();
  $(#form + (this.value)).fadeIn(slow);
  }
  }
  });
 });

 $contype being the form from the previous page which was selected,
 this is so it shows the correct form errors.

 Thanks alot

   

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] IE bug or bug in my code ?

2007-03-20 Thread spinnach

i've also had issues with this, not only in ie but sometimes in firefox 
too.. and ie 67 occasionally crashed or couldn't load the page when 
using $().ready() so now i just call the init function from the footer 
of the page.. i know it's kind of ugly but it works every time and 
doesn't crash :)..

oh and it sometimes happens for me on http://jquery.com/api too 
($().ready not firing - both in ie67 and firefox2)..

dennis.

Jack Killpatrick wrote:
 FWIW, I've had issues in IE 6/7 with $(document).ready() not firing 
 something in it's function. I've never dug into exactly why it happens, 
 but found a workaround using setTimeout, like this:
 
 $(document).ready(function() {
 setTimeout(
 function(){
your code that isn't firing in IE here
 }
 , ( $.browser.msie ) ? 500 : 0
 )
 });
 
 So, maybe give that a try. FWIW, we (me and the folks I work with) found 
 that 500ms seemed to do the trick, but 100ms didn't.
 
 Also, If anyone knows why that's needed for some things to fire via 
 $(document).ready, I'd love to know. We've also worked around it by 
 doing these things:
 
 1. putting our $(document).ready at the end of the HTML page (after the 
 objects that we need ready).
 2. used setTimeout() to check for the presence of the object(s) we need 
 ready, and when they become ready, binding to them.
 
 - Jack
 



___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] IE bug or bug in my code ?

2007-03-20 Thread abba bryant


Have you both double checked your doc-types? And your markup? The only time I
have found ready to fail was when I was either in quirks mode or my dom was
mangled somehow.

Abba



spinnach wrote:
 
 i've also had issues with this, not only in ie but sometimes in firefox 
 too.. and ie 67 occasionally crashed or couldn't load the page when 
 using $().ready() so now i just call the init function from the footer 
 of the page.. i know it's kind of ugly but it works every time and 
 doesn't crash :)..
 
 oh and it sometimes happens for me on http://jquery.com/api too 
 ($().ready not firing - both in ie67 and firefox2)..
 
 dennis.
 
 Jack Killpatrick wrote:
 FWIW, I've had issues in IE 6/7 with $(document).ready() not firing 
 something in it's function. I've never dug into exactly why it happens, 
 but found a workaround using setTimeout, like this:
 
 $(document).ready(function() {
 setTimeout(
 function(){
your code that isn't firing in IE here
 }
 , ( $.browser.msie ) ? 500 : 0
 )
 });
 
 So, maybe give that a try. FWIW, we (me and the folks I work with) found 
 that 500ms seemed to do the trick, but 100ms didn't.
 
 Also, If anyone knows why that's needed for some things to fire via 
 $(document).ready, I'd love to know. We've also worked around it by 
 doing these things:
 
 1. putting our $(document).ready at the end of the HTML page (after the 
 objects that we need ready).
 2. used setTimeout() to check for the presence of the object(s) we need 
 ready, and when they become ready, binding to them.
 
 - Jack
 
 
 
 
 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/
 
 

-- 
View this message in context: 
http://www.nabble.com/IE-bug-or-bug-in-my-code---tf3432817.html#a9579831
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] IE bug or bug in my code ?

2007-03-20 Thread Jack Killpatrick

I think mine were using 4.0 (or 4.01) transitional, and I did not have 
the option to switch that to XHTML.


- Jack

abba bryant wrote:

Have you both double checked your doc-types? And your markup? The only time I
have found ready to fail was when I was either in quirks mode or my dom was
mangled somehow.

Abba



spinnach wrote:
  
i've also had issues with this, not only in ie but sometimes in firefox 
too.. and ie 67 occasionally crashed or couldn't load the page when 
using $().ready() so now i just call the init function from the footer 
of the page.. i know it's kind of ugly but it works every time and 
doesn't crash :)..


oh and it sometimes happens for me on http://jquery.com/api too 
($().ready not firing - both in ie67 and firefox2)..


dennis.

Jack Killpatrick wrote:

FWIW, I've had issues in IE 6/7 with $(document).ready() not firing 
something in it's function. I've never dug into exactly why it happens, 
but found a workaround using setTimeout, like this:


$(document).ready(function() {
setTimeout(
function(){
   your code that isn't firing in IE here
}
, ( $.browser.msie ) ? 500 : 0
)
});

So, maybe give that a try. FWIW, we (me and the folks I work with) found 
that 500ms seemed to do the trick, but 100ms didn't.


Also, If anyone knows why that's needed for some things to fire via 
$(document).ready, I'd love to know. We've also worked around it by 
doing these things:


1. putting our $(document).ready at the end of the HTML page (after the 
objects that we need ready).
2. used setTimeout() to check for the presence of the object(s) we need 
ready, and when they become ready, binding to them.


- Jack

  


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/





  
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] IE bug or bug in my code ?

2007-03-20 Thread spinnach

yup, all my doctypes are xhtml1.0 transitional, all markup 100% valid..

dennis.

abba bryant wrote:
 Have you both double checked your doc-types? And your markup? The only time I
 have found ready to fail was when I was either in quirks mode or my dom was
 mangled somehow.
 
 Abba
 
 
 
 spinnach wrote:
 i've also had issues with this, not only in ie but sometimes in firefox 
 too.. and ie 67 occasionally crashed or couldn't load the page when 
 using $().ready() so now i just call the init function from the footer 
 of the page.. i know it's kind of ugly but it works every time and 
 doesn't crash :)..

 oh and it sometimes happens for me on http://jquery.com/api too 
 ($().ready not firing - both in ie67 and firefox2)..

 dennis.

 Jack Killpatrick wrote:
 FWIW, I've had issues in IE 6/7 with $(document).ready() not firing 
 something in it's function. I've never dug into exactly why it happens, 
 but found a workaround using setTimeout, like this:

 $(document).ready(function() {
 setTimeout(
 function(){
your code that isn't firing in IE here
 }
 , ( $.browser.msie ) ? 500 : 0
 )
 });

 So, maybe give that a try. FWIW, we (me and the folks I work with) found 
 that 500ms seemed to do the trick, but 100ms didn't.

 Also, If anyone knows why that's needed for some things to fire via 
 $(document).ready, I'd love to know. We've also worked around it by 
 doing these things:

 1. putting our $(document).ready at the end of the HTML page (after the 
 objects that we need ready).
 2. used setTimeout() to check for the presence of the object(s) we need 
 ready, and when they become ready, binding to them.

 - Jack



 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/


 


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] dimensions plugin Mozilla bug

2007-03-20 Thread Brandon Aaron

After some investigating, I'm not able to reproduce what you describe.
Could you possibly post up or send me a test case for this? The
highest the loop should go to is the body tag (in Mozilla). Once it
hits the body tag inside the loop you describe the code that gives you
an error *should* not run. Also, you might want to insure you have the
latest revision: 1485.

Thanks
--
Brandon Aaron

On 3/18/07, Brandon Aaron [EMAIL PROTECTED] wrote:
 Thanks for the bug ... I'll get this fixed soon!

 --
 Brandon Aaorn

 On 3/18/07, Wizzud [EMAIL PROTECTED] wrote:
 
  While playing with Ext I encountered a problem in Firefox whereby the offset
  function in dimensions was causing an elem.style error. The reason is that
  there is a do-while loop if options.scroll is set, and that loop will go all
  the way up to the document, at which point - if the browser is Mozilla - the
  code attempts to check the css for overflow not visible and falls over
  because document has no style.
  I fixed this in my version by modifying line 260 of dimensions.js and
  inserting a check for op, so the line now begins ...
 
  if (op  jQuery.browser.mozilla  
 
  This prevents the jQuery.css() call failing at the document level.
  --
  View this message in context: 
  http://www.nabble.com/dimensions-plugin-Mozilla-bug-tf3421935.html#a9537545
  Sent from the jQuery Plugins mailing list archive at Nabble.com.
 
 
  ___
  jQuery mailing list
  discuss@jquery.com
  http://jquery.com/discuss/
 


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] dimensions plugin Mozilla bug

2007-03-18 Thread Brandon Aaron

Thanks for the bug ... I'll get this fixed soon!

--
Brandon Aaorn

On 3/18/07, Wizzud [EMAIL PROTECTED] wrote:

 While playing with Ext I encountered a problem in Firefox whereby the offset
 function in dimensions was causing an elem.style error. The reason is that
 there is a do-while loop if options.scroll is set, and that loop will go all
 the way up to the document, at which point - if the browser is Mozilla - the
 code attempts to check the css for overflow not visible and falls over
 because document has no style.
 I fixed this in my version by modifying line 260 of dimensions.js and
 inserting a check for op, so the line now begins ...

 if (op  jQuery.browser.mozilla  

 This prevents the jQuery.css() call failing at the document level.
 --
 View this message in context: 
 http://www.nabble.com/dimensions-plugin-Mozilla-bug-tf3421935.html#a9537545
 Sent from the jQuery Plugins mailing list archive at Nabble.com.


 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Possible next()/prev() bug?

2007-03-18 Thread John Resig

.next() and .prev() only work with the next (or previous) /immediate/
element. In your example, the next element is actually a br/ - which
your filter doesn't match.

Currently there isn't a way to do what you want (easily) in jQuery.
I'd imagine it being something like .nextClosest(div.myDiv). The
next best thing that I can think of would be to do:

$(this).next().next(div.myDiv)

Hope that helps.

--John

On 3/18/07, EvanT [EMAIL PROTECTED] wrote:

 Hi all,

 I've come across what is possibly a bug (or unexpected behaviour) when using
 next().

 I have an example page setup here: http://fapdragon.com/test/test.html

 As far as I can see, the filter for next() is not being applied and it
 always returns the next DOM element.

 Can anyone comment on this or should I log a ticket for it?

 Thanks,
 Evan
 --
 View this message in context: 
 http://www.nabble.com/Possible-next%28%29-prev%28%29-bug--tf3422183.html#a9538163
 Sent from the JQuery mailing list archive at Nabble.com.


 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Possible next()/prev() bug?

2007-03-18 Thread EvanT


Thanks John,

I thought it might have been the case, the documentation is a little
ambiguous.

It would be nice to see a function like $(selector).after(filter) that finds
the next matching element (I know that after is already used for DOM
manipulation) and a similar one for prev()

Cheers,
Evan


John Resig wrote:
 
 .next() and .prev() only work with the next (or previous) /immediate/
 element. In your example, the next element is actually a br/ - which
 your filter doesn't match.
 
 Currently there isn't a way to do what you want (easily) in jQuery.
 I'd imagine it being something like .nextClosest(div.myDiv). The
 next best thing that I can think of would be to do:
 
 $(this).next().next(div.myDiv)
 
 Hope that helps.
 
 --John
 
 On 3/18/07, EvanT [EMAIL PROTECTED] wrote:

 Hi all,

 I've come across what is possibly a bug (or unexpected behaviour) when
 using
 next().

 I have an example page setup here: http://fapdragon.com/test/test.html

 As far as I can see, the filter for next() is not being applied and it
 always returns the next DOM element.

 Can anyone comment on this or should I log a ticket for it?

 Thanks,
 Evan
 --
 View this message in context:
 http://www.nabble.com/Possible-next%28%29-prev%28%29-bug--tf3422183.html#a9538163
 Sent from the JQuery mailing list archive at Nabble.com.


 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/

 
 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/
 
 

-- 
View this message in context: 
http://www.nabble.com/Possible-next%28%29-prev%28%29-bug--tf3422183.html#a9543998
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Odd include ordering bug w/ Tablesorter and WrapInner

2007-02-28 Thread Christian Bach


2007/2/26, Jonathan Freeman [EMAIL PROTECTED]:


Haven't had the time to debug this but if you include the
jquery-plugin-wrapinner.js before the jquery.tablesorter.js (see below)
then the wrapinner will not work. However, reverse the two and both work
successfully.



This is a bit unclear, but the tablesorter plugin provides it's own
implementation of wrapInner.

This will be removed  in the next update.

Best regards
Christian Bach
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Odd include ordering bug w/ Tablesorter and WrapInner

2007-02-28 Thread Jonathan Freeman

Hmmm, makes sense now with the wrapinner implementation within
tablesorter. Sorry for the confusion, maybe this is better ...

Wrap Inner works:
script src=jquery.tablesorter.js type=text/javascript/script
script src=jquery-plugin-wrapinner.js type=text/javascript/script

Wrap Inner does not work:
script src=jquery-plugin-wrapinner.js type=text/javascript/script
script src=jquery.tablesorter.js type=text/javascript/script


--- Christian Bach [EMAIL PROTECTED] wrote:

 2007/2/26, Jonathan Freeman [EMAIL PROTECTED]:
 
  Haven't had the time to debug this but if you include the
  jquery-plugin-wrapinner.js before the jquery.tablesorter.js (see
 below)
  then the wrapinner will not work. However, reverse the two and both
 work
  successfully.
 
 
 This is a bit unclear, but the tablesorter plugin provides it's own
 implementation of wrapInner.
 
 This will be removed  in the next update.
 
 Best regards
 Christian Bach
  ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/
 



 

Sucker-punch spam with award-winning protection. 
Try the free Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/features_spam.html

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] possible slideUp/slideDown bug?

2007-02-28 Thread cdvrooman


Let me clarify my intent:
I have two users, a Superuser with only a superuser right, and a plain
User who may have 1 or many rights.

If the Superuser radio button is selected, then I want the available
permision list to slideUp, because no other rights need to be selected.
However, if the User radio button is selected, then I want to make the
list of possible user associated rights visible via slideDown. 

That is why I opted to not use slideToggle because clicking on either radio
button would either show or hide the permission_block depending on its last
state.

Do you see where I am going now? That's why I want to only permit the
slideDown to fire when the condition of the permission_block is hidden,
and vice versa for slideUp.

Cheers,
 Christopher.

P.S. I'm using (1) to make the block show or hide itself as fast as
possible.

However, while on the subject... although I'm using
$(document).ready(function() { } to hide the block when a user already has
the Superuser right (and shouldn't see the other permissions), I still
briefly see the permissions_block right before it hides itself. I thought it
should already be hidden by the time the page loads itself? Or do I have to
set its css to block:hidden ? Thanks.



John Resig wrote:
 
 jQuery already has a slide toggle:
 http://docs.jquery.com/Effects#slideToggle.28_speed.2C_callback_.29
 
 There's no reason to use a plugin for it.
 
 @Christopher - Your final code would look something like this:
 
$(document).ready(function() {
// Attach toggle function:
$(#user_type_super_x).click(function() {
$(#permision_block).slideToggle(1000);
});
});
 
 I think you meant to do 1000 instead of 1 - all jQuery animations are
 measured in milliseconds. Of course, you could also do something like:
 slow instead.
 
 --John
 
 On 2/26/07, FreakDev [EMAIL PROTECTED] wrote:
 hi,

 i don't really understand your code, you define two different function
 for
 the same click event...

 you should check SlideToggleDown function from Interface 1.2

  http://interface.eyecon.ro/demos/ifx.html#slide-fx
 http://interface.eyecon.ro/docs/fx

 ++

 FreakDev


 On 2/26/07, cdvrooman [EMAIL PROTECTED] wrote:
 
  Hello,
I am using slideUp and slideDown, with each attached to a radio
 button
 via
  click(). Here is the code:
  $(document).ready(function() {
  // Attach hide/show functions:
 
 $(#user_type_super_x).click(function() {
 
 $(#permision_block).slideUp(1);
  });
 
 $(#user_type_user_x).click(function() {
 
 $(#permision_block).slideDown(1);
  });
  });
 
 
After I click on the first radio button and slideUp the content, if
 I
  click on the same button again, the content appears and then slidesUp
 again.
 
If the content is already hidden, shouldn't it by default not be
 possible
  to make it appear again (however briefly) by repeated applications of
 the
  slideUp function?
 
The same is true for slideDown. After sliding down the content, I can
 make
  it slideDown repeatedly.
 
Should I check the height or transparency first before permitting
  slideUp/slideDown to fire?
 
Thanks,
Christopher.
  --
  View this message in context:
 http://www.nabble.com/possible-slideUp-slideDown-bug--tf3296684.html#a9170964
  Sent from the JQuery mailing list archive at Nabble.com.
 
 

-- 
View this message in context: 
http://www.nabble.com/possible-slideUp-slideDown-bug--tf3296684.html#a9240156
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] possible slideUp/slideDown bug?

2007-02-26 Thread FreakDev


hi,

i don't really understand your code, you define two different function for
the same click event...

you should check SlideToggleDown function from Interface 1.2

http://interface.eyecon.ro/demos/ifx.html#slide-fx
http://interface.eyecon.ro/docs/fx

++

FreakDev

On 2/26/07, cdvrooman [EMAIL PROTECTED] wrote:



Hello,
  I am using slideUp and slideDown, with each attached to a radio button
via
click(). Here is the code:
$(document).ready(function() {
// Attach hide/show functions:
$(#user_type_super_x).click(function() {
$(#permision_block).slideUp(1);
});
$(#user_type_user_x).click(function() {
$(#permision_block).slideDown(1);
});
});


  After I click on the first radio button and slideUp the content, if I
click on the same button again, the content appears and then slidesUp
again.

  If the content is already hidden, shouldn't it by default not be
possible
to make it appear again (however briefly) by repeated applications of the
slideUp function?

  The same is true for slideDown. After sliding down the content, I can
make
it slideDown repeatedly.

  Should I check the height or transparency first before permitting
slideUp/slideDown to fire?

  Thanks,
  Christopher.
--
View this message in context:
http://www.nabble.com/possible-slideUp-slideDown-bug--tf3296684.html#a9170964
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] possible slideUp/slideDown bug?

2007-02-26 Thread John Resig

jQuery already has a slide toggle:
http://docs.jquery.com/Effects#slideToggle.28_speed.2C_callback_.29

There's no reason to use a plugin for it.

@Christopher - Your final code would look something like this:

   $(document).ready(function() {
   // Attach toggle function:
   $(#user_type_super_x).click(function() {
   $(#permision_block).slideToggle(1000);
   });
   });

I think you meant to do 1000 instead of 1 - all jQuery animations are
measured in milliseconds. Of course, you could also do something like:
slow instead.

--John

On 2/26/07, FreakDev [EMAIL PROTECTED] wrote:
 hi,

 i don't really understand your code, you define two different function for
 the same click event...

 you should check SlideToggleDown function from Interface 1.2

  http://interface.eyecon.ro/demos/ifx.html#slide-fx
 http://interface.eyecon.ro/docs/fx

 ++

 FreakDev


 On 2/26/07, cdvrooman [EMAIL PROTECTED] wrote:
 
  Hello,
I am using slideUp and slideDown, with each attached to a radio button
 via
  click(). Here is the code:
  $(document).ready(function() {
  // Attach hide/show functions:
 
 $(#user_type_super_x).click(function() {
 
 $(#permision_block).slideUp(1);
  });
 
 $(#user_type_user_x).click(function() {
 
 $(#permision_block).slideDown(1);
  });
  });
 
 
After I click on the first radio button and slideUp the content, if I
  click on the same button again, the content appears and then slidesUp
 again.
 
If the content is already hidden, shouldn't it by default not be
 possible
  to make it appear again (however briefly) by repeated applications of the
  slideUp function?
 
The same is true for slideDown. After sliding down the content, I can
 make
  it slideDown repeatedly.
 
Should I check the height or transparency first before permitting
  slideUp/slideDown to fire?
 
Thanks,
Christopher.
  --
  View this message in context:
 http://www.nabble.com/possible-slideUp-slideDown-bug--tf3296684.html#a9170964
  Sent from the JQuery mailing list archive at Nabble.com.
 
 
  ___
  jQuery mailing list
  discuss@jquery.com
  http://jquery.com/discuss/
 


 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/



___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] possible slideUp/slideDown bug?

2007-02-26 Thread rolfsf


or maybe just use slideToggle (Interface not needed)

Rolf



FreakDev wrote:
 
 hi,
 
 i don't really understand your code, you define two different function for
 the same click event...
 
 you should check SlideToggleDown function from Interface 1.2
 
 http://interface.eyecon.ro/demos/ifx.html#slide-fx
 http://interface.eyecon.ro/docs/fx
 
 ++
 
 FreakDev
 
 On 2/26/07, cdvrooman [EMAIL PROTECTED] wrote:


 Hello,
   I am using slideUp and slideDown, with each attached to a radio button
 via
 click(). Here is the code:
 $(document).ready(function() {
 // Attach hide/show functions:
 $(#user_type_super_x).click(function() {
 $(#permision_block).slideUp(1);
 });
 $(#user_type_user_x).click(function() {
 $(#permision_block).slideDown(1);
 });
 });


   After I click on the first radio button and slideUp the content, if I
 click on the same button again, the content appears and then slidesUp
 again.

   If the content is already hidden, shouldn't it by default not be
 possible
 to make it appear again (however briefly) by repeated applications of the
 slideUp function?

   The same is true for slideDown. After sliding down the content, I can
 make
 it slideDown repeatedly.

   Should I check the height or transparency first before permitting
 slideUp/slideDown to fire?

   Thanks,
   Christopher.
 --
 View this message in context:
 http://www.nabble.com/possible-slideUp-slideDown-bug--tf3296684.html#a9170964
 Sent from the JQuery mailing list archive at Nabble.com.


 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/

 
 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/
 
 

-- 
View this message in context: 
http://www.nabble.com/possible-slideUp-slideDown-bug--tf3296684.html#a9171527
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] 1.1 add(this) bug?

2007-01-15 Thread John Resig

Yep, this has been reported:
http://jquery.com/dev/bugs/bug/806/

We should have a full fix (1.1.1) by this next weekend.

--John

On 1/15/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
 previously I coded

 $(this).parents().add(this) inside a bind('click' function...

 then continue the chain to look at 'me and my parents'
 on 1.1 the chain only has the parents, this did not get added.

 when I break it up , with an .end() and continue the chain, it brings
 'me' back to the chain, and I have to each thru  this separately.

 What did I miss?


 $(this)
 .attr(target,elsewhere)
 .parents()
 .prev('code.json')
 .each(jsonize)
 .end()
 .end()
 .prev('code.json')
 .each(jsonize)
 works, but
 $(this)
 .attr(target,elsewhere)
 .parents()
 .add(this)
 .prev('code.json')
 .each(jsonize)
 does not.

 --
 Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] 1.1 add(this) bug?

2007-01-15 Thread Ⓙⓐⓚⓔ

great! I'll keep a watch out for that bug close, and pick it up the svn!

On 1/15/07, John Resig [EMAIL PROTECTED] wrote:
 Yep, this has been reported:
 http://jquery.com/dev/bugs/bug/806/

 We should have a full fix (1.1.1) by this next weekend.

 --John

 On 1/15/07, Ⓙⓐⓚⓔ [EMAIL PROTECTED] wrote:
  previously I coded
 
  $(this).parents().add(this) inside a bind('click' function...
 
  then continue the chain to look at 'me and my parents'
  on 1.1 the chain only has the parents, this did not get added.
 
  when I break it up , with an .end() and continue the chain, it brings
  'me' back to the chain, and I have to each thru  this separately.
 
  What did I miss?
 
 
  $(this)
  .attr(target,elsewhere)
  .parents()
  .prev('code.json')
  .each(jsonize)
  .end()
  .end()
  .prev('code.json')
  .each(jsonize)
  works, but
  $(this)
  .attr(target,elsewhere)
  .parents()
  .add(this)
  .prev('code.json')
  .each(jsonize)
  does not.
 
  --
  Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
  ___
  jQuery mailing list
  discuss@jquery.com
  http://jquery.com/discuss/
 
 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/



-- 
Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] JQuery 1.1a - changes/bug? with $(this).id

2007-01-08 Thread Sam Collett

On 08/01/07, Olaf Bosch [EMAIL PROTECTED] wrote:
 Hi, thank you all for 1.1

 i begin to testing, this works in 1.0.4

 $(document).ready(function() {
   $('textarea').each(function(i) {
   $(this).id('area_'+i).after('span
 id=gro_'+i+'grouml;szlig;er\/span');
   });

 FireBug say $(this).id is not a function

 What is to do?
 --
 Viele Grüße, Olaf

 ---
 [EMAIL PROTECTED]
 http://olaf-bosch.de
 www.akitafreund.de
 ---

It was taken out of jQuery 1.1. Try

$(this).attr('id', 'area_'+i)

Which should also work in jQuery 1.0.4

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] JQuery 1.1a - changes/bug? with $(this).id

2007-01-08 Thread Mike Alsup

 FireBug say $(this).id is not a function

 What is to do?

You'll need to rewrite that as:  $(this).attr(id)

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] JQuery 1.1a - changes/bug? with $(this).id

2007-01-08 Thread Klaus Hartl

Olaf Bosch schrieb:
 Hi, thank you all for 1.1
 
 i begin to testing, this works in 1.0.4
 
 $(document).ready(function() {
   $('textarea').each(function(i) {
   $(this).id('area_'+i).after('span 
 id=gro_'+i+'grouml;szlig;er\/span');
   });
 
 FireBug say $(this).id is not a function
 
 What is to do?

First of all *before* switching to a new/massively changed API read the 
changelog/blog post[1].

Afterwards you will know that most of the helper methods have been wiped 
away ;-)

Try:
$(this).attr('id', 'area_'+i)


[1] http://jquery.com/blog/2007/01/08/jquery-11a/


-- Klaus



___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] JQuery 1.1a - changes/bug? with $(this).id

2007-01-08 Thread Olaf Bosch

Klaus Hartl schrieb:

 First of all *before* switching to a new/massively changed API read the 
 changelog/blog post[1].

Yes, i have, sorry i realese not that ID ar also a ATTR ;)

 Try:
 $(this).attr('id', 'area_'+i)

Thanks all.

Next Problem:

$(textarea).css('height') give before 1.1 110 now i became 110px
i would have 110 for summary 110+50
must i strip the px self or give a JQuery-Way?

-- 
Viele Grüße, Olaf

---
[EMAIL PROTECTED]
http://olaf-bosch.de
www.akitafreund.de
---

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] JQuery 1.1a - changes/bug? with $(this).id

2007-01-08 Thread Klaus Hartl

Olaf Bosch schrieb:
 Klaus Hartl schrieb:
 
 First of all *before* switching to a new/massively changed API read the 
 changelog/blog post[1].
 
 Yes, i have, sorry i realese not that ID ar also a ATTR ;)
 
 Try:
 $(this).attr('id', 'area_'+i)
 
 Thanks all.
 
 Next Problem:
 
 $(textarea).css('height') give before 1.1 110 now i became 110px
 i would have 110 for summary 110+50
 must i strip the px self or give a JQuery-Way?
 

I think you have to parse it yourself...:

var h = parseInt($(textarea).css('height'));

You could also try this (if you like chaining better):

String.prototype.parseInt = function() {
 var i = parseInt(this);
 return !isNaN(i)  i || 0;
};

$(textarea).css('height').parseInt();


-- Klaus


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] JQuery 1.1a - changes/bug? with $(this).id

2007-01-08 Thread Olaf Bosch

Klaus Hartl schrieb:

 I think you have to parse it yourself...:
 
 var h = parseInt($(textarea).css('height'));

Great, works perfect, Thank you


-- 
Viele Grüße, Olaf

---
[EMAIL PROTECTED]
http://olaf-bosch.de
www.akitafreund.de
---

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is it a bug

2006-12-13 Thread Johnny


hi,guys

i get a form in table by jquery.

if the form like this:

table
 form
 tbodytbody
 /form
/table

The table does not display in firefox(i use ff2.0), but it's ok in IE.
and i can find the table of dom from DOM inspector add-on,  it does
exists!!

i try some lots of ways to find what happened. And last i find.

if html like this:
formtabletbodytbody/table /form

it can display in ff2.

note: it just happens when you get html in ajax, but it's okay
accessing directly by ff2

I'm sorry my poor English:)
Johnny 



Johnny wrote:
 
 Hi, guys
 
 I have a problem when i use jquery's ajax module.
 
 My jquery code is here:
 
 $(document).ready(function() {
   $(div#test).load(xml_to_page.jsp,{class:Img,sn:1});
  });
 
 xml_to_page.jsp is file transform xml to html
 
  String xml = \\xml\\ + class + .xml;
  String xsl =  \\xml\\item_attr_form.xsl;
 try {
 XSLTHelper.transform(xml, xsl, out);
 } catch ( Exception e ) {
 e.printStackTrace(response.getWriter());
 }
 
 it works in IE, it can display html created by the xml_to_page.jsp , but
 it doesn't display in FireFox, and i use DOM Inspect, the div#test
 actually have content.
 
 So where is the problem?
 
 Thank you advance!
 
 Johnny
 

-- 
View this message in context: 
http://www.nabble.com/Is-it-a-bug-tf2805700.html#a7848698
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is it a bug

2006-12-13 Thread Erik Beeson


You may want to consider looking into using jXs:
http://www.malsup.com/jquery/jxs/

The problem is XML doesn't work like HTML when inserted into the DOM, even
though it looks like HTML. I hacked up some code from jXs to convert the XML
into HTML and made it a little plugin called htmlify. I use it like this:

$.get('/ajax/foo', params, function(data) {
   if($('success', data).size()  0) {
   $('#result').prepend($('success', data).children().htmlify());
   } else {
   ...
   }
});

The returned XML looks like:
successdiv class=foospanSome stuff/span/div/success


The plugin is just hacked up stuff from jXs:

jQuery.fn.htmlify = function() {
   if(this.size() == 1) {
   return jQuery(makeElement(this.get(0)));
   } else {
   var htmlifyNodes = [];
   this.each(function() {
   var temp = makeElement(this);
   htmlifyNodes.push(temp);
   });
   return jQuery(htmlifyNodes);
   }

   function makeElement(xmlNode) {
   switch(xmlNode.nodeType) {
   case 1:  // element
   return element(xmlNode);
   case 3:  // text
   case 4:  // cdata -- Corrected by Mike Alsup 07/26/2006
   var t = xmlNode.nodeValue.replace(/^\s+|\s+$/g,  ); //
condense white space
   return t.length  1 ? undefined : document.createTextNode
(t);
   default:
   return undefined; // do nothing;
   }
   function element(xNode) {
   var node = document.createElement(xNode.tagName);
   for(var i = 0, a = xNode.attributes; i  a.length; i++) {
   jQuery(node).attr(a[i].nodeName, a[i].nodeValue);
   }
   for(var i = 0, c = xNode.childNodes; i  c.length; i++) {
   var child = makeElement(c[i]);
   if(child) {
   node.appendChild(child);
   }
   }
   if(node.metaDone) {
   node.metaDone = undefined;
   }
   return node;
   }
   }
};

It probably totally breaks on IE. I haven't tried it yet.

--Erik

On 12/13/06, Johnny [EMAIL PROTECTED] wrote:



hi,guys

i get a form in table by jquery.

if the form like this:

table
form
tbodytbody
/form
/table

The table does not display in firefox(i use ff2.0), but it's ok in IE.
and i can find the table of dom from DOM inspector add-on,  it does
exists!!

i try some lots of ways to find what happened. And last i find.

if html like this:
formtabletbodytbody/table /form

it can display in ff2.

note: it just happens when you get html in ajax, but it's okay
accessing directly by ff2

I'm sorry my poor English:)
Johnny



Johnny wrote:

 Hi, guys

 I have a problem when i use jquery's ajax module.

 My jquery code is here:

 $(document).ready(function() {
   $(div#test).load(xml_to_page.jsp,{class:Img,sn:1});
  });

 xml_to_page.jsp is file transform xml to html

  String xml = \\xml\\ + class + .xml;
  String xsl =  \\xml\\item_attr_form.xsl;
 try {
 XSLTHelper.transform(xml, xsl, out);
 } catch ( Exception e ) {
 e.printStackTrace(response.getWriter());
 }

 it works in IE, it can display html created by the xml_to_page.jsp , but

 it doesn't display in FireFox, and i use DOM Inspect, the div#test
 actually have content.

 So where is the problem?

 Thank you advance!

 Johnny


--
View this message in context:
http://www.nabble.com/Is-it-a-bug-tf2805700.html#a7848698
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is it a bug

2006-12-13 Thread Klaus Hartl

Johnny schrieb:
 hi,guys
 
 i get a form in table by jquery.
 
 if the form like this:
 
 table
  form
  tbodytbody
  /form
 /table
 
 The table does not display in firefox(i use ff2.0), but it's ok in IE.
 and i can find the table of dom from DOM inspector add-on,  it does
 exists!!
 
 i try some lots of ways to find what happened. And last i find.
 
 if html like this:
 formtabletbodytbody/table /form
 
 it can display in ff2.
 
 note: it just happens when you get html in ajax, but it's okay
 accessing directly by ff2
 
 I'm sorry my poor English:)
 Johnny 


tableform ... /form/table is invalid HTML. Put that into a 
static page and test it on the W3C validator.

In a static page you can get away with that because the browsers tag 
soup parser will fix your bad HTML. It's another thing obviously if you 
try to append such broken HTML with JavaScript after the page has been 
loaded/rendered. Imagine you were a browser: You're expecting a tbody or 
tr element after the table has been opened but there comes a form 
suddenly - where to put it? After the table? Close the table immediatly 
and open the form? IE seems to be more error prone here but that doesn't 
matter.

So it's not a jQuery bug, the bug is your HTML itself. As you already 
found out, just use formtable ... /table/form and you're fine.


-- Klaus

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is it a bug

2006-12-13 Thread Karl Swedberg


Johnny,

If you really need that table in there, try rearranging your HTML so  
that the form element is inside one of the table's cells:


table
tbody
  tr
td
  form ... /form
/td
  /tr
/tbody
/table


--Karl
_
Karl Swedberg
www.englishrules.com
www.learningjquery.com



On Dec 13, 2006, at 4:58 AM, Michael Holloway wrote:


if the form like this:

table
form
tbodytbody
/form
/table

The table does not display in firefox(i use ff2.0), but it's ok in IE.
and i can find the table of dom from DOM inspector add-on, it does
exists!!

i try some lots of ways to find what happened. And last i find.

if html like this:
formtabletbodytbody/table /form



Hi Johnny,
Your first code example is incorrect html markup, the second method is
better. This is not a bug in jQuery.
Cheers,
Mike.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is it a bug

2006-12-13 Thread johnnybai


Thanks. i put form element outsidest:)

On 12/13/06, Karl Swedberg [EMAIL PROTECTED] wrote:


Johnny,
If you really need that table in there, try rearranging your HTML so that
the form element is inside one of the table's cells:

table
tbody
  tr
td
  form ... /form
/td
  /tr
/tbody
/table


--Karl
_
Karl Swedberg
www.englishrules.com
www.learningjquery.com



On Dec 13, 2006, at 4:58 AM, Michael Holloway wrote:

if the form like this:

table
form
tbodytbody
/form
/table

The table does not display in firefox(i use ff2.0), but it's ok in IE.
and i can find the table of dom from DOM inspector add-on, it does
exists!!

i try some lots of ways to find what happened. And last i find.

if html like this:
formtabletbodytbody/table /form



Hi Johnny,
Your first code example is incorrect html markup, the second method is
better. This is not a bug in jQuery.
Cheers,
Mike.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/



___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/



___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is it a bug

2006-12-12 Thread Brice Burgess

Johnny wrote:
 it works in IE, it can display html created by the xml_to_page.jsp , but it
 doesn't display in FireFox, and i use DOM Inspect, the div#test actually
 have content.
   
Johnny,
  Does:

$().ready(function() {
  $(div#test).load(xml_to_page.jsp,{class:Img,sn:1}).show();
});

  Fix show the content? Maybe there's a CSS rule hiding the div?

~ Brice


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is it a bug

2006-12-12 Thread Johnny


nope, it display correctly in ie, but it doesn't display in firefox. it must
not be the problem of css

Brice Burgess wrote:
 
 Johnny wrote:
 it works in IE, it can display html created by the xml_to_page.jsp , but
 it
 doesn't display in FireFox, and i use DOM Inspect, the div#test actually
 have content.
   
 Johnny,
   Does:
 
 $().ready(function() {
   $(div#test).load(xml_to_page.jsp,{class:Img,sn:1}).show();
 });
 
   Fix show the content? Maybe there's a CSS rule hiding the div?
 
 ~ Brice
 
 
 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/
 
 

-- 
View this message in context: 
http://www.nabble.com/Is-it-a-bug-tf2805700.html#a7846989
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is it a bug

2006-12-11 Thread Erik Beeson




doesn't display in FireFox, and i use DOM Inspect, the div#test actually
have content.



Are you saying the div DOES have content, it just isn't displaying?

--Erik
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is it a bug

2006-12-11 Thread Johnny


yeah


Erik Beeson wrote:
 


 doesn't display in FireFox, and i use DOM Inspect, the div#test actually
 have content.
 
 
 Are you saying the div DOES have content, it just isn't displaying?
 
 --Erik
 
 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/
 
 

-- 
View this message in context: 
http://www.nabble.com/Is-it-a-bug-tf2805700.html#a7827978
Sent from the JQuery mailing list archive at Nabble.com.


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] datePicker plugin - inputClick bug fix and other alterations

2006-11-27 Thread Brandon Aaron

On 11/27/06, Sam Collett [EMAIL PROTECTED] wrote:
 Along with that, I have reduced the number of times 'attr' is used:

 i.e.
 $(a).attr({'title' : 'Foo', 'rel'  : 'myrel', 'href' : 'javascript:;'})

 becomes:
 $(a).title('Foo').rel('myrel').href('javascript:;')

I'm curious why you have done this?

Those helper methods might be deprecated from the core in the 1.1 release.

--
Brandon Aaron

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] datePicker plugin - inputClick bug fix and other alterations

2006-11-27 Thread Sam Collett

On 27/11/06, Brandon Aaron [EMAIL PROTECTED] wrote:
 On 11/27/06, Sam Collett [EMAIL PROTECTED] wrote:
  Along with that, I have reduced the number of times 'attr' is used:
 
  i.e.
  $(a).attr({'title' : 'Foo', 'rel'  : 'myrel', 'href' : 'javascript:;'})
 
  becomes:
  $(a).title('Foo').rel('myrel').href('javascript:;')

 I'm curious why you have done this?

 Those helper methods might be deprecated from the core in the 1.1 release.

 --
 Brandon Aaron

I've changed it to use attr to set attributes (addClass is still used
to set the class) and noticed that 'val' was used instead of attr to
get the value (so that has been fixed too). Download link is till the
same.

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Possible IE7 fadeOut bug

2006-10-20 Thread Chris Ovenden

I forgot to say that if you uncomment the alert, it gives undefined in IE7.

On 10/20/06, Chris Ovenden [EMAIL PROTECTED] wrote:
 Hi

 I have a problem where fadeOut is undefined in IE7 (final), but
 working fine in Firefox (2.0RC3).

 The relevant code is:
 //alert(this.clickBlock.fadeOut);
 clickBlock.fadeOut(slow, function() {
  $(this).remove();
 });

 clickBlock is a regular  jQuery object defined earlier by

 clickBlock = $(document.createElement(div)).id(block);

 I originally had clickBlock.remove(); here and it worked just fine.

 Can't check in IE6 at present, so don't know if it only affects IE7.

 If someone can confirm this as a bug, I'll file a bug report.

 --
 Chris Ovenden

 http://thepeer.blogspot.com
 Imagine all the people / Sharing all the world



-- 
Chris Ovenden

http://thepeer.blogspot.com
Imagine all the people / Sharing all the world

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Possible IE7 fadeOut bug

2006-10-20 Thread Chris Ovenden

On 10/20/06, Chris Ovenden [EMAIL PROTECTED] wrote:
 I forgot to say that if you uncomment the alert, it gives undefined in IE7.

alert should read alert(clickBlock.fadeOut); // no 'this'

 On 10/20/06, Chris Ovenden [EMAIL PROTECTED] wrote:
  Hi
 
  I have a problem where fadeOut is undefined in IE7 (final), but
  working fine in Firefox (2.0RC3).
 
  The relevant code is:
  //alert(this.clickBlock.fadeOut);
  clickBlock.fadeOut(slow, function() {
   $(this).remove();
  });
 
  clickBlock is a regular  jQuery object defined earlier by
 
  clickBlock = $(document.createElement(div)).id(block);
 
  I originally had clickBlock.remove(); here and it worked just fine.
 
  Can't check in IE6 at present, so don't know if it only affects IE7.
 
  If someone can confirm this as a bug, I'll file a bug report.
 
  --
  Chris Ovenden
 
  http://thepeer.blogspot.com
  Imagine all the people / Sharing all the world
 


 --
 Chris Ovenden

 http://thepeer.blogspot.com
 Imagine all the people / Sharing all the world



-- 
Chris Ovenden

http://thepeer.blogspot.com
Imagine all the people / Sharing all the world

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Possible IE7 fadeOut bug

2006-10-20 Thread Brandon Aaron

Could you also try doing an alert(clickBlock.css) and alert(clickBlock.animate)?

Thanks

--
Brandon Aaron

On 10/20/06, Chris Ovenden [EMAIL PROTECTED] wrote:
 On 10/20/06, Chris Ovenden [EMAIL PROTECTED] wrote:
  I forgot to say that if you uncomment the alert, it gives undefined in 
  IE7.
 
 alert should read alert(clickBlock.fadeOut); // no 'this'

  On 10/20/06, Chris Ovenden [EMAIL PROTECTED] wrote:
   Hi
  
   I have a problem where fadeOut is undefined in IE7 (final), but
   working fine in Firefox (2.0RC3).
  
   The relevant code is:
   //alert(this.clickBlock.fadeOut);
   clickBlock.fadeOut(slow, function() {
$(this).remove();
   });
  
   clickBlock is a regular  jQuery object defined earlier by
  
   clickBlock = $(document.createElement(div)).id(block);
  
   I originally had clickBlock.remove(); here and it worked just fine.
  
   Can't check in IE6 at present, so don't know if it only affects IE7.
  
   If someone can confirm this as a bug, I'll file a bug report.
  
   --
   Chris Ovenden
  
   http://thepeer.blogspot.com
   Imagine all the people / Sharing all the world
  
 
 
  --
  Chris Ovenden
 
  http://thepeer.blogspot.com
  Imagine all the people / Sharing all the world
 


 --
 Chris Ovenden

 http://thepeer.blogspot.com
 Imagine all the people / Sharing all the world

 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Possible IE7 fadeOut bug

2006-10-20 Thread Chris Ovenden

Interesting - .css returned a function value, but .animate was
undefined. I'm pretty sure the animation module is in there, though,
as it's working in FF, and indeed (checking) FF returns the expected
function.

On 10/20/06, Brandon Aaron [EMAIL PROTECTED] wrote:
 Could you also try doing an alert(clickBlock.css) and 
 alert(clickBlock.animate)?

 Thanks

 --
 Brandon Aaron

 On 10/20/06, Chris Ovenden [EMAIL PROTECTED] wrote:
  On 10/20/06, Chris Ovenden [EMAIL PROTECTED] wrote:
   I forgot to say that if you uncomment the alert, it gives undefined in 
   IE7.
  
  alert should read alert(clickBlock.fadeOut); // no 'this'
 
   On 10/20/06, Chris Ovenden [EMAIL PROTECTED] wrote:
Hi
   
I have a problem where fadeOut is undefined in IE7 (final), but
working fine in Firefox (2.0RC3).
   
The relevant code is:
//alert(this.clickBlock.fadeOut);
clickBlock.fadeOut(slow, function() {
 $(this).remove();
});
   
clickBlock is a regular  jQuery object defined earlier by
   
clickBlock = $(document.createElement(div)).id(block);
   
I originally had clickBlock.remove(); here and it worked just fine.
   
Can't check in IE6 at present, so don't know if it only affects IE7.
   
If someone can confirm this as a bug, I'll file a bug report.
   
--
Chris Ovenden
   
http://thepeer.blogspot.com
Imagine all the people / Sharing all the world
   
  
  
   --
   Chris Ovenden
  
   http://thepeer.blogspot.com
   Imagine all the people / Sharing all the world
  
 
 
  --
  Chris Ovenden
 
  http://thepeer.blogspot.com
  Imagine all the people / Sharing all the world
 
  ___
  jQuery mailing list
  discuss@jquery.com
  http://jquery.com/discuss/
 

 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/



-- 
Chris Ovenden

http://thepeer.blogspot.com
Imagine all the people / Sharing all the world

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] I'm find a bug in jQuery??s Cookie plugIn

2006-10-17 Thread Jörn Zaefferer

Klaus Hartl schrieb:
 Klaus Hartl schrieb:
   
 cookie deletion does not work with more than one cookie, will fix that...
 

 False alarm, forget that - I just screwed my test page. Should put up 
 automatic tests in there if possible.

 Jörn or John, where can I get some information about the test suite used 
 in jQuery?
   
I started some stuff here: http://jquery.com/docs/DevelopersGuide/
Not yet very much, but perhaps enough to get you started.

-- Jörn

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] I'm find a bug in jQuery??s Cookie plugIn

2006-10-16 Thread Klaus Hartl



Microtoby schrieb:
 I'm find a bug in jQuery's Cookie plugIn.
 
 When you write more than 2 cookies, from the second, you could not read 
 it value correctly.
 
 It's because read document.cookie is cookie1=val1; cookie2=val2, 
 behind ;, there is a blank. So the source code line 72 cause error if 
 ( cookie.substring(0, name.length + 1) == (name + '=')).
 
 Fix it, just modify line 68:
 
 Old style: var cookies = document.cookie.split(';');
 
 New style: var cookies = document.cookie.replace(; , ;).split(';');
 
  Regards,
 
 Microtoby

Thanks for the catch, I fixed that in SVN. I modified line 70:

var cookie = $.trim(cookies[i]);


-- Klaus

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] I'm find a bug in jQuery??s Cookie plugIn

2006-10-16 Thread Sam Collett

On 16/10/06, Klaus Hartl [EMAIL PROTECTED] wrote:


 Microtoby schrieb:
  I'm find a bug in jQuery's Cookie plugIn.
 
  When you write more than 2 cookies, from the second, you could not read
  it value correctly.
 
  It's because read document.cookie is cookie1=val1; cookie2=val2,
  behind ;, there is a blank. So the source code line 72 cause error if
  ( cookie.substring(0, name.length + 1) == (name + '=')).
 
  Fix it, just modify line 68:
 
  Old style: var cookies = document.cookie.split(';');
 
  New style: var cookies = document.cookie.replace(; , ;).split(';');
 
   Regards,
 
  Microtoby

 Thanks for the catch, I fixed that in SVN. I modified line 70:

 var cookie = $.trim(cookies[i]);


 -- Klaus

Shouldn't that be:

jQuery.trim(cookies[i])

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] I'm find a bug in jQuery??s Cookie plugIn

2006-10-16 Thread Klaus Hartl

Klaus Hartl schrieb:
 cookie deletion does not work with more than one cookie, will fix that...

False alarm, forget that - I just screwed my test page. Should put up 
automatic tests in there if possible.

Jörn or John, where can I get some information about the test suite used 
in jQuery?


-- Klaus

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Highlight fade plugin bug

2006-10-05 Thread Blair Mitchelmore

That's pretty weird, the page works in firefox but not IE. I'll have to 
investigate in a bit; at the moment I've got a large scale software 
engineering assignment due...

-blair

Rafael Santos wrote:
 hey, have you faced this bug?

 http://blocparty.com.br/js/teste2.html

 Should that happen?

 

 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Highlight fade plugin bug

2006-10-05 Thread Blair Mitchelmore

OK, in what can officially be called the stupidest mistake ever, my 
regex tested for #FFF before #FF so all 6 char colour strings got 
caught and made into a 3 char so your F0F0F0 became F0F and therefore 
purple... I've fixed the code in the unpacked version at 
http://jquery.offput.ca/js/jquery.highlightFade.js but I'll have to get 
home before I can get a chance to upload a new packed version...

Man do I feel stupid... and amazed that this wasn't caught until now...

-blair

Still gonna look into that table cell highlighting issue later on as well...

Rafael Santos wrote:
 Yeah, it works on IE, but i didnt mention the real bug. This purple 
 color is not defined.. lol


 2006/10/5, Blair Mitchelmore [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED] :

 That's pretty weird, the page works in firefox but not IE. I'll
 have to
 investigate in a bit; at the moment I've got a large scale software
 engineering assignment due...

 -blair

 Rafael Santos wrote:
  hey, have you faced this bug?
 
  http://blocparty.com.br/js/teste2.html
 
  Should that happen?
 
 
 
 
  ___
  jQuery mailing list
  discuss@jquery.com mailto:discuss@jquery.com
  http://jquery.com/discuss/


 ___
 jQuery mailing list
 discuss@jquery.com mailto:discuss@jquery.com
 http://jquery.com/discuss/



 

 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Highlight fade plugin bug

2006-10-05 Thread Blair Mitchelmore

OK, I uploaded a new packed version and just in case it mattered, your 
highlightFade code could be made prettier by setting some useful default 
values:

$.highlightFade.defaults['speed'] = 1000;
$.highlightFade.defaults['iterator'] = 'exponential';
$('td.link1').click(function() { $(this).highlightFade('#33') });
$('td.link1').hover(function() { $(this).highlightFade('#F0F0F0') 
},function() { return true });

-blair

Blair Mitchelmore wrote:
 OK, in what can officially be called the stupidest mistake ever, my 
 regex tested for #FFF before #FF so all 6 char colour strings got 
 caught and made into a 3 char so your F0F0F0 became F0F and therefore 
 purple... I've fixed the code in the unpacked version at 
 http://jquery.offput.ca/js/jquery.highlightFade.js but I'll have to get 
 home before I can get a chance to upload a new packed version...

 Man do I feel stupid... and amazed that this wasn't caught until now...

 -blair

 Still gonna look into that table cell highlighting issue later on as well...

 Rafael Santos wrote:
 Yeah, it works on IE, but i didnt mention the real bug. This purple 
 color is not defined.. lol


 2006/10/5, Blair Mitchelmore [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED] :

 That's pretty weird, the page works in firefox but not IE. I'll
 have to
 investigate in a bit; at the moment I've got a large scale software
 engineering assignment due...

 -blair

 Rafael Santos wrote:
  hey, have you faced this bug?
 
  http://blocparty.com.br/js/teste2.html
 
  Should that happen?
 
 
 
 
  ___
  jQuery mailing list
  discuss@jquery.com mailto:discuss@jquery.com
  http://jquery.com/discuss/


 ___
 jQuery mailing list
 discuss@jquery.com mailto:discuss@jquery.com
 http://jquery.com/discuss/



 

 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/


 ___
 jQuery mailing list
 discuss@jquery.com
 http://jquery.com/discuss/


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Highlight fade plugin bug

2006-10-05 Thread Rafael Santos

nice one man...Thanks a lot2006/10/5, Blair Mitchelmore [EMAIL PROTECTED]:
OK, I uploaded a new packed version and just in case it mattered, yourhighlightFade code could be made prettier by setting some useful defaultvalues:$.highlightFade.defaults['speed'] = 1000;$.highlightFade.defaults['iterator'] = 'exponential';
$('td.link1').click(function() { $(this).highlightFade('#33') });$('td.link1').hover(function() { $(this).highlightFade('#F0F0F0')},function() { return true });-blairBlair Mitchelmore wrote:
 OK, in what can officially be called the stupidest mistake ever, my regex tested for #FFF before #FF so all 6 char colour strings got caught and made into a 3 char so your F0F0F0 became F0F and therefore
 purple... I've fixed the code in the unpacked version at http://jquery.offput.ca/js/jquery.highlightFade.js but I'll have to get home before I can get a chance to upload a new packed version...
 Man do I feel stupid... and amazed that this wasn't caught until now... -blair Still gonna look into that table cell highlighting issue later on as well... Rafael Santos wrote:
 Yeah, it works on IE, but i didnt mention the real bug. This purple color is not defined.. lol 2006/10/5, Blair Mitchelmore 
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] : That's pretty weird, the page works in firefox but not IE. I'll have to
 investigate in a bit; at the moment I've got a large scale software engineering assignment due... -blair Rafael Santos wrote:  hey, have you faced this bug?
   http://blocparty.com.br/js/teste2.html   Should that happen? 
     ___  jQuery mailing list
  discuss@jquery.com mailto:discuss@jquery.com  http://jquery.com/discuss/
 ___ jQuery mailing list discuss@jquery.com mailto:
discuss@jquery.com http://jquery.com/discuss/ 
 ___ jQuery mailing list discuss@jquery.com 
http://jquery.com/discuss/ ___ jQuery mailing list discuss@jquery.com 
http://jquery.com/discuss/___jQuery mailing listdiscuss@jquery.comhttp://jquery.com/discuss/

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is this a bug in XPath support?

2006-09-13 Thread limodou

On 9/13/06, Nigel [EMAIL PROTECTED] wrote:
 This doesn't work:
 $([EMAIL PROTECTED]'bea-portal-layout-placeholder'][3])

 I had to do it like this:
 $([EMAIL PROTECTED]'bea-portal-layout-placeholder']:eq(3))

yeah. I think [3] should be used as:

$([EMAIL PROTECTED]'bea-portal-layout-placeholder'])[3]

-- 
I like python!
My Blog: http://www.donews.net/limodou
UliPad Site: http://wiki.woodpecker.org.cn/moin/UliPad
UliPad Maillist: http://groups.google.com/group/ulipad

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] Is this a bug in XPath support?

2006-09-13 Thread limodou

On 9/14/06, John Resig [EMAIL PROTECTED] wrote:
  yeah. I think [3] should be used as:
 
  $([EMAIL PROTECTED]'bea-portal-layout-placeholder'])[3]

 That doesn't give you what you want. That returns a DOM element, not a
 jQuery object - a thus breaks the chain.

you are right. I don't know what' the next he want. But I think if you
want to use [3], the above should be the correct.

-- 
I like python!
My Blog: http://www.donews.net/limodou
UliPad Site: http://wiki.woodpecker.org.cn/moin/UliPad
UliPad Maillist: http://groups.google.com/group/ulipad

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] jquery 1st space bug while working with classes

2006-08-08 Thread Anton

ok, but it'll require some time to create simplest testcase

 That's a weird one, do you think you could create a bug report for it?
 http://proj.jquery.com/dev/bugs/new/

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] jquery 1st space bug while working with classes

2006-08-08 Thread Klaus Hartl


 td.white.active{
 background:#FFF;
 border-color:#F00;
 }
  
  
 P.S. - i'm not sure, but i guess the same bug appears in IE either


IE does not support the multiple class selector .white.active. It may 
seem so somehow, because here it applies these styles as if you had written

td.active

But if you have another rule in your style sheet after this rule that 
goes like

td.red.active {
 background: red;
 border-color: #f00;
}

the background of every element with the class active would become red 
in IE.


Oh, another hint: class names like white, red, small etc. are purely 
presentational. if the background shall be changed sometime, you will 
have to change the class name as well to let it still make sense. and 
that's what css isn't about. so you better use semantic class names that 
are not derived from the current (!) look, but from the function or 
structural meaning of that element (for example important, subtotal etc.)


Regards, Klaus


___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] jquery 1st space bug while working with classes

2006-08-08 Thread Klaus Hartl


 while in FF elements className after series of events states: white active
 in Opera the same element after same events has classNames:  active white
  
 so in Opera this styles won't apply for this element (while FF behaves 
 as expected):
 td.white.active{
 background:#FFF;
 border-color:#F00;
 }

To clarify: This is because multiple classes do also cascade. Thus 
class=white active isn't the same as class=active white.

If both classes one and two of an element define the same 
properties, the later class overwrites the first:

.one { color: green; }
.two { color: blue; }

p class=one twoBlue text/p
p class=two oneGreen text/p

And thus the selector .white.active does not match class=active white.


Regards, Klaus




___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

52 matches

Mail list logo