[jquery-dev] Re: Anybody here like curry?
I too noticed the omission of this feature, and found it strange. -- Már -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
Re: [jquery-dev] Re: jQueryLINT
On Mon, Jan 18, 2010 at 1:23 AM, James Padolsey wrote: > I don't think we can attribute the idea to any one person though. As > Matt mentioned, this topic comes up every few months, from various > individuals. I haven't followed all threads about this topic, but it seems we got pretty in-depth with this one, pushing you to wire something together. I'm also confident if we got so much deeper this time, it's probably due to older threads, too :-) > Also, what's with the "you have to" attitude. Politeness isn't > overrated, ya know... While I agree there're better ways to phrase the same concept, I think his "you have to" may come from imperfect knowledge of English - but I might be wrong on this one. Cheers, -- Andrea Raimondi Senior Software Analyst&Developer -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] Re: Feature Request: css rules
Thank you Karl, that seems to be exactly what I was looking for! @Andrea... I know it's potentially a bit of a rare case but I've had to make some changes to an old page where the css was static but the page had rows (not table rows) that needed to be able to update based on the width of the page, but because certain other parts needed to be static widths it became impossible to give them a percent width or anything else like that. They don't have a special parent element that can be set where they can be 100% either so the easiest way was to set the widths to a static number every resize, but I also had to include a catch every time new rows were added, and this would allow me to get rid of the extra step. As a side note it also seemed to be a bit faster (at least in some browsers) when I was able to set it via class instead of jquery iterating through the elements and setting each one (though I haven't tested with 1.4). Thanks for the replies though! -Mike On Jan 16, 9:11 am, Andrea Raimondi wrote: > On Fri, Jan 15, 2010 at 10:03 PM, Mike wrote: > > I think it would be nice to be able to create permanent rules in CSS, > > so that if I were to change the style of any specific type of element, > > it could have a permanent effect on all newly created elements as > > well. > > Hi Mike, > > Maybe it's just I didn't sleep enough today(happens often) but I am not > sure > what's the usefulness of what you want to do? > CSS rules can be set for tags regardless of the creation moment(iirc at > least). > > Wait, maybe I am seeing what you mean: you want to be able to change > f.i. the class of a tag in the > whole page, including newly created elements? If so, what's the > usefulness of the thing? > I can't see why you would want to do something like that, at least - I > can't see a reason considering that's not > something(IMVHO) you should do in general :-) > > Rgds, > > -- > Andrea Raimondi > Senior Software Analyst&Developer -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] Re: jQueryLINT
You're right. I just added this thread URL to the source.
I don't think we can attribute the idea to any one person though. As
Matt mentioned, this topic comes up every few months, from various
individuals.
Also, what's with the "you have to" attitude. Politeness isn't
overrated, ya know...
On Jan 17, 11:47 pm, DBJDBJ wrote:
> James, In your source You have to mention whose idea was this
> And where have you found out about it : this forum + this thread ...
>
> Thanks : DBJ
>
> On Jan 17, 9:22 pm, James Padolsey
> wrote:
>
>
>
> > Yesterday, after seeing this thread, I started work on a "jQuery Lint"
> > script. You can see it here:http://github.com/jamespadolsey/jQuery-Lint
>
> > It does a few basic checks - argument signatures being the main one.
> > It also tries to combat lack-of-caching with selections, and it will
> > warn you when your selection returns nothing. It'll also suggest that
> > you use attr({...})/css({...} instead of css().css().css().css() ...
>
> > I've added a simple API via which you can add special checks. For
> > example:
>
> > jQuery.LINT.special[1].jQuery = function(selector, context) {
> > if (selector === '*') {return "Don't use the universal
> > selector!"; }
> > // Everything is fine... don't return anything (or return true)
>
> > };
>
> > So, potentially, one of you could create a bunch of these "special
> > checks" and release them all as a separate script which can be slotted
> > in with Lint.
>
> > It's been made to work with Firebug, but you can quite easily slot in
> > your own console mechanism via jQuery.LINT.console.
>
> > Like I said, this was started yesterday, so it's still got a few
> > kinks...
>
> > On Jan 15, 7:53 pm, Matt wrote:
>
> > > On Jan 15, 1:11 pm, Scott Sauyet wrote:
>
> > > > I like the idea, and I think it would be possible to do this as a
> > > > plug-in, which replaces calls to jQuery functions with calls that
> > > > check the parameters, store errors, then delegate to the the original
> > > > function. But have no time at the moment to help implement it.
>
> > > Check the archives. This comes up every few months, everyone agrees it
> > > would be cool, everyone agrees it could be implemented relatively
> > > easily, yet no one wants to spend the time to build, test, and release
> > > it. Bummer.
>
> > > Matt Kruse
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] Re: jQueryLINT
James, In your source You have to mention whose idea was this
And where have you found out about it : this forum + this thread ...
Thanks : DBJ
On Jan 17, 9:22 pm, James Padolsey
wrote:
> Yesterday, after seeing this thread, I started work on a "jQuery Lint"
> script. You can see it here:http://github.com/jamespadolsey/jQuery-Lint
>
> It does a few basic checks - argument signatures being the main one.
> It also tries to combat lack-of-caching with selections, and it will
> warn you when your selection returns nothing. It'll also suggest that
> you use attr({...})/css({...} instead of css().css().css().css() ...
>
> I've added a simple API via which you can add special checks. For
> example:
>
> jQuery.LINT.special[1].jQuery = function(selector, context) {
> if (selector === '*') {return "Don't use the universal
> selector!"; }
> // Everything is fine... don't return anything (or return true)
>
> };
>
> So, potentially, one of you could create a bunch of these "special
> checks" and release them all as a separate script which can be slotted
> in with Lint.
>
> It's been made to work with Firebug, but you can quite easily slot in
> your own console mechanism via jQuery.LINT.console.
>
> Like I said, this was started yesterday, so it's still got a few
> kinks...
>
> On Jan 15, 7:53 pm, Matt wrote:
>
> > On Jan 15, 1:11 pm, Scott Sauyet wrote:
>
> > > I like the idea, and I think it would be possible to do this as a
> > > plug-in, which replaces calls to jQuery functions with calls that
> > > check the parameters, store errors, then delegate to the the original
> > > function. But have no time at the moment to help implement it.
>
> > Check the archives. This comes up every few months, everyone agrees it
> > would be cool, everyone agrees it could be implemented relatively
> > easily, yet no one wants to spend the time to build, test, and release
> > it. Bummer.
>
> > Matt Kruse
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en.
Re: [jquery-dev] 1.4: xhr.readyState assignment crash (ajax.js line 461)
Replied over in the forum.
--John
On Sun, Jan 17, 2010 at 4:53 PM, Steven Black wrote:
> (Re-posted here since there is currently zero traction on the new
> forum)
>
> I have a question about code in ajax.js that is crashing for me in
> both FF (latest) and IE (latest).
>
> The code below starts on line 453 of th ajax.js module. -- (Note: In
> the released build this line ended-up at line number 4983 of
> jquery-1.4.js)
>
> My questions are
>
> 1) Why the try {} around the function definition? That doesn't seem
> right, but I've been wrong before :-)
>
> 2) The crash is not caught by the try{}
>
> The offending line is #461
>
> (461) xhr.readyState = 0;
>
> The error as reported by the FireBug console: "setting a property that
> has only a getter".
>
> Anyone have insight to share? When I comment-out that line everything
> works perfectly.
>
> Here is a clip of the code in ajax.js starting at line #453
>
> (453) // Override the abort handler, if we can (IE doesn't allow it,
> but that's OK)
> // Opera doesn't fire onreadystatechange at all on abort
> try {
> var oldAbort = xhr.abort;
> xhr.abort = function() {
> if ( xhr ) {
> oldAbort.call( xhr );
> if ( xhr ) {
> xhr.readyState = 0; // Boom!
> }
> }
>
> onreadystatechange();
> };
> } catch(e) { }
>
> --
> You received this message because you are subscribed to the Google Groups
> "jQuery Development" group.
> To post to this group, send email to jquery-...@googlegroups.com.
> To unsubscribe from this group, send email to
> jquery-dev+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/jquery-dev?hl=en.
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] 1.4: xhr.readyState assignment crash (ajax.js line 461)
(Re-posted here since there is currently zero traction on the new
forum)
I have a question about code in ajax.js that is crashing for me in
both FF (latest) and IE (latest).
The code below starts on line 453 of th ajax.js module. -- (Note: In
the released build this line ended-up at line number 4983 of
jquery-1.4.js)
My questions are
1) Why the try {} around the function definition? That doesn't seem
right, but I've been wrong before :-)
2) The crash is not caught by the try{}
The offending line is #461
(461)xhr.readyState = 0;
The error as reported by the FireBug console: "setting a property that
has only a getter".
Anyone have insight to share? When I comment-out that line everything
works perfectly.
Here is a clip of the code in ajax.js starting at line #453
(453) // Override the abort handler, if we can (IE doesn't allow it,
but that's OK)
// Opera doesn't fire onreadystatechange at all on abort
try {
var oldAbort = xhr.abort;
xhr.abort = function() {
if ( xhr ) {
oldAbort.call( xhr );
if ( xhr ) {
xhr.readyState = 0; // Boom!
}
}
onreadystatechange();
};
} catch(e) { }
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] Re: jQueryLINT
Yesterday, after seeing this thread, I started work on a "jQuery Lint"
script. You can see it here: http://github.com/jamespadolsey/jQuery-Lint
It does a few basic checks - argument signatures being the main one.
It also tries to combat lack-of-caching with selections, and it will
warn you when your selection returns nothing. It'll also suggest that
you use attr({...})/css({...} instead of css().css().css().css() ...
I've added a simple API via which you can add special checks. For
example:
jQuery.LINT.special[1].jQuery = function(selector, context) {
if (selector === '*') {return "Don't use the universal
selector!"; }
// Everything is fine... don't return anything (or return true)
};
So, potentially, one of you could create a bunch of these "special
checks" and release them all as a separate script which can be slotted
in with Lint.
It's been made to work with Firebug, but you can quite easily slot in
your own console mechanism via jQuery.LINT.console.
Like I said, this was started yesterday, so it's still got a few
kinks...
On Jan 15, 7:53 pm, Matt wrote:
> On Jan 15, 1:11 pm, Scott Sauyet wrote:
>
> > I like the idea, and I think it would be possible to do this as a
> > plug-in, which replaces calls to jQuery functions with calls that
> > check the parameters, store errors, then delegate to the the original
> > function. But have no time at the moment to help implement it.
>
> Check the archives. This comes up every few months, everyone agrees it
> would be cool, everyone agrees it could be implemented relatively
> easily, yet no one wants to spend the time to build, test, and release
> it. Bummer.
>
> Matt Kruse
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en.
Re: [jquery-dev] Re: [OT] Maybe it's not yet time to move to the forums...
The new forum is jquery-en, jquery-ui, jquery-dev, and jquery-ui-dev combined. So yes, we will be directing people away to the new one in a couple days. We're still working on some outstanding issues but we hope to get them resolved soon. --John On Sun, Jan 17, 2010 at 11:16 AM, Kevin Dalman wrote: > Still sending confirmation emails as of Jan 17. However I never got > the first one and had to go to accounts page and click 'send again' - > worked that time. > > It is a little confusing as to which 'group' the new forum is supposed > to be? It is only the dev group or BOTH the general and dev groups > combined? > > /Kevin > > On Jan 16, 6:32 am, John Resig wrote: >> It sounds like confirmation emails are still being sent out - it also >> sounds like they're having some server troubles at the moment, making >> the confirmation email/login process a bit troublesome. I would >> recommend being patient while they get this sorted out. >> >> --John >> >> On Sat, Jan 16, 2010 at 7:55 AM, Andrea Raimondi >> >> >> >> wrote: >> > XP Pro latest updates >> > FF 3.5.7 >> >> > Trying to view recent posts. >> > "Loading..." window appears. >> >> > I am logged in with username/password. >> > Haven't yet confirmed my account(I can't because I didn't receive the >> > confirmation email yet). >> >> > Nothing besides the loading... window happens. >> >> > Two likely possibilites: >> >> > 1) The forum has a tad of problems >> > 2) I have to confirm the account >> >> > Which one is correct? >> >> > Rgds, >> >> > -- >> > Andrea Raimondi >> > Senior Software Analyst&Developer >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "jQuery Development" group. >> > To post to this group, send email to jquery-...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > jquery-dev+unsubscr...@googlegroups.com. >> > For more options, visit this group >> > athttp://groups.google.com/group/jquery-dev?hl=en.- Hide quoted text - >> >> - Show quoted text - > > -- > You received this message because you are subscribed to the Google Groups > "jQuery Development" group. > To post to this group, send email to jquery-...@googlegroups.com. > To unsubscribe from this group, send email to > jquery-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/jquery-dev?hl=en. > > > > -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] Re: [OT] Maybe it's not yet time to move to the forums...
Still sending confirmation emails as of Jan 17. However I never got the first one and had to go to accounts page and click 'send again' - worked that time. It is a little confusing as to which 'group' the new forum is supposed to be? It is only the dev group or BOTH the general and dev groups combined? /Kevin On Jan 16, 6:32 am, John Resig wrote: > It sounds like confirmation emails are still being sent out - it also > sounds like they're having some server troubles at the moment, making > the confirmation email/login process a bit troublesome. I would > recommend being patient while they get this sorted out. > > --John > > On Sat, Jan 16, 2010 at 7:55 AM, Andrea Raimondi > > > > wrote: > > XP Pro latest updates > > FF 3.5.7 > > > Trying to view recent posts. > > "Loading..." window appears. > > > I am logged in with username/password. > > Haven't yet confirmed my account(I can't because I didn't receive the > > confirmation email yet). > > > Nothing besides the loading... window happens. > > > Two likely possibilites: > > > 1) The forum has a tad of problems > > 2) I have to confirm the account > > > Which one is correct? > > > Rgds, > > > -- > > Andrea Raimondi > > Senior Software Analyst&Developer > > > -- > > You received this message because you are subscribed to the Google Groups > > "jQuery Development" group. > > To post to this group, send email to jquery-...@googlegroups.com. > > To unsubscribe from this group, send email to > > jquery-dev+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/jquery-dev?hl=en.- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] Using hide('slide') will DESTROY most UI Widgets!
If a UI widget like Tabs or Accordion is inside a DIV that is hidden
and reshown using $(elem).hide('slide') and $(elem).show('slide'), the
widget is completely destroyed! In other words, all widgets styles and
events are removed.
This bug does not occur when using slideToggle().
Here is a demo page that shows the issues:
http://layout.jquery-dev.net/demos/tabs_jq14_test.html
/Kevin
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] Re: Binding "change" on an select though .live() doesn't seem to work in IE using jQuery 1.4
I have looked into this. The "trigger-line" in the testChange-function has to be changed from this: return jQuery.event.trigger( e, arguments[1], this ); to this: return jQuery.event.trigger( e, arguments[1], elem ); Additional It seems, that there was a typo. The condition above contains the following statement: elem.type !== "select" wich is always true. I think this can be deleted, without problems. On 16 Jan., 14:34, mape wrote: > The example works fine in Firefox 3.6, Safari 4.0.4 and Chrome > 4.0.295.0 dev. > > Doesn't seem to work in IE8 (native) and IE6, IE7 (though IEtester). > > http://mape.me/jquery/select-live-ie/ -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] Re: Bug in 1.4rc1 $.extend
Well, I've got your point, and changed my code to var data =
jQuery.extend(true, [], arrComp);
With that, I wanted to make a copy of "arrComp" into "data", so that
deleting something in data won's mess with arrComp, right?
Testing like you did (and even if I make arrComp.toSource() , copy the
content and paste directly in my code, like:)
var arrComp = [{name:'One', value:1}, {name:'Two', value:2}];
var data = jQuery.extend(true, [], arrComp);
It works! Deleting something in data won't change arrComp. But in my
real case, it doesn't work! When I delete something in the data, it
deletes from arrComp as well. I don't know how could I show you this,
I've been trying to reproduce this in small scale, but I had no
success.
If it happens to me to find out a better simulation, I will post here
again. Thanks for you help, though!
On Jan 14, 2:44 am, Dave Methvin wrote:
> > x[1] = {twist: 3};
> > alert( x.toSource() ); // [{test:1}, {twist:3}]
>
> My test case was broken! When I change it to this:
>
> var x = [ {test:1}, {toast:2} ];
> var y = $.extend(true, [], x);
> x[1].toast = 3;
> alert( y.toSource() );
>
> I get the expected output:
>
> [{test:1}, {toast:2}]
>
> That is, x was deep-extended to y and a change to x didn't affect y.
>
> So it seems like that should work. Can you show more of the code?
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en.
[jquery-dev] Re: aborting Ajax calls the success callback
> I think calling error: with a statusText of "abort" would be the more > intuitive way of handling this. Sorry, why should you want to handle abort the same way you handle an error? If you intentional abort a request, it stops/completes, but i don´t see an error in this. Why not simply use the complete event/ callback with status "abort". -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
