I am planning on using the ui datepicker component in an app with
multi-calendar requirements.
This includes the datepicker UI component, meaning that the datepicker
should be able to render with a completely different
calendar (such as Julian or Coptic) as well as the current localized text
suppor
Just found this site that gives a lot of information about vsdoc:
http://weblogs.asp.net/bleroy/archive/2007/04/23/the-format-for-javascript-doc-comments.aspx
On 18 feb, 12:53, jerone wrote:
> Don't know if it's worth mentioning, but I found some small bugs in
> the vsdoc for jQuery:
> - line ~8
No problem - glad it's working for you, now!
--John
On Wed, Feb 18, 2009 at 1:41 PM, GreyCells wrote:
>
> My apologies for using the dev forum as a user forum :)
>
> Many thanks John for this - in 1.2 it was the only was I (rightly or
> wrongly) could get the id of the first parent fieldset t
My apologies for using the dev forum as a user forum :)
Many thanks John for this - in 1.2 it was the only was I (rightly or
wrongly) could get the id of the first parent fieldset that had an id
- it was a bit of a shock that is slowed down so much in 1.3. Having
said that, the issue is now mute
> I noticed. Great!
>
> One question though...
> Does this also fix the problem of the source/prototype element being
> *moved* to the first target location, rather than cloned like in
> 1.2.6 ?
That was actually a bug in 1.2.6 - it was resolved in 1.3.
For example, this moves this element:
$("#
Are you sure you meant :has([id])? That would find all fieldsets that
have a descendant that has an ID attribute (which is pretty costly).
It sounds like you could replace that line with:
jQuery(this).closest("fieldset[id]")
--John
On Wed, Feb 18, 2009 at 11:34 AM, GreyCells wrote:
>
> I'm
> This has been fixed - FYI.
I noticed. Great!
One question though...
Does this also fix the problem of the source/prototype element being
*moved* to the first target location, rather than cloned like in
1.2.6 ?
--
Már
--~--~-~--~~~---~--~~
You received this mes
Right now it says "Set a local timeout in ms for the request." I just
changed it to: "Set a local timeout (in milliseconds) for the
request."
--John
On Wed, Feb 18, 2009 at 10:19 AM, Drolh wrote:
>
> Please add to the documentation the scale for numeric values. In the
> AJAX section (http://
Just a quick note- I tried using last nights nightly (2-17), to see if
it would fix the clone issues I was having in IE with 1.3.1. However,
it seems to lock up Safari completely somewhere in the middle of my js
execution. Not sure exactly what caused it, and will investigate more
when I have a ch
I'm sure this is not the most elegant line of code, but in 1.2.6,
there was no performance hit (i.e. a moderately complex page/form
loaded in the blink of an eye). In 1.3.1 this now takes > 10 seconds
with 100% cpu:
var parentWithIdAttribute = jQuery(this).parents('fieldset:has
([id]):first').att
Please add to the documentation the scale for numeric values. In the
AJAX section (http://docs.jquery.com/Ajax/jQuery.ajax) in the options
section there is a timeout option described but there is no mention
what the default is or what the scale is (in this case it is
milliseconds).
Thanks.
--~-
This has been fixed - FYI.
--John
On Wed, Feb 18, 2009 at 4:10 AM, Már Örlygsson wrote:
>
>> it looks like it may be a duplicate of this one:
>
> It is. I did my due diligence search a few days ago, and didn't find
> any tickets back then.
> Great to see this is being taken care of!
> Thanks.
So fadeIn only works when it's element is displayed none and doesn't
check at all if it's element has a changed opacity?
Doesn't it make more sense if fadeIn checks for it's current opacity
and fades from there;
jQuery(this).fadeTo(2000, 0.25).fadeIn(2000);
I say that because if I use fadeOut in
Yep, there's a bug filed on this here:
http://dev.jquery.com/ticket/3549
In the meantime you can get around it by just binding them separately
(using separate .bind calls).
--John
On Wed, Feb 18, 2009 at 9:28 AM, dooge.zh wrote:
>
> When i use $().bind to bind a event handler of two event ty
fadeIn won't have an effect if it's already visible (it'll fire
instantly). fadeIn takes a hidden (display: none) element and changes
its opacity to 1 over the time frame.
If you're looking to fade to 0.25 over 2 seconds, then fade to 1 over
2 seconds I'd do:
jQuery(this).fadeTo(0.25, 2000).fad
When i use $().bind to bind a event handler of two event type at one
time like this:
var o = $("#myObj");
o.bind("mouseover.a.b mouseout.a.c", function(){});
then handler registrations of the two types of event in the $.cache
use the same handler, and its type is set to the last ty
I'm not that familiar with jQuery yet, so I wanted to pass this trough
you guys first.
Shouldn't this work with both a interval of 2 seconds:
jQuery("p").click(function() { jQuery(this).fadeTo(2000, 0.25, function
() { alert("2 seconds later => PASSED"); jQuery(this).fadeIn(2000,
function() { ale
Don't know if it's worth mentioning, but I found some small bugs in
the vsdoc for jQuery:
- line ~835 (html function) the param name should be 'value' instead
of 'val'.
- line ~866 (eq function) the param name should be 'i' instead of
'num'.
Secondly I like to know if there's going to be document
> There was a brief discussion about binding to the current context
> rather than document, which is similar to what you are suggesting:
>
> http://groups.google.com/group/jquery-dev/browse_thread/thread/911a50d2a0ed64b9
>
> John, should I raise a ticket for this?
Sure. I already have it on my to
There was a brief discussion about binding to the current context
rather than document, which is similar to what you are suggesting:
http://groups.google.com/group/jquery-dev/browse_thread/thread/911a50d2a0ed64b9
John, should I raise a ticket for this?
On Feb 17, 9:21 am, weepy wrote:
> Re th
> it looks like it may be a duplicate of this one:
It is. I did my due diligence search a few days ago, and didn't find
any tickets back then.
Great to see this is being taken care of!
Thanks.
--
Már
--~--~-~--~~~---~--~~
You received this message because you are
21 matches
Mail list logo
