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
cont
On Fri, Jan 15, 2010 at 8:28 PM, "Cowboy" Ben Alman wrote:
> jquery.ajaxSettings.traditional is undefined by default, but since we
> only test its value in a "truthy" way, it shouldn't matter whether it
> defaults to false or undefined. Defaulting to undefined safes a few
> bytes.
>
Ok, I expect
Both jQuery 1.3.2 and 1.4 urlencode the name and value parts, which
shouldn't cause any problems.
jquery.ajaxSettings.traditional is undefined by default, but since we
only test its value in a "truthy" way, it shouldn't matter whether it
defaults to false or undefined. Defaulting to undefined safe
I'm going to have to move back to working code here shortly, this is a
production server. I'll try to get the offending code off to another
location so you can have a look at it.
Thanks
Zack Kitzmiller
On Jan 13, 8:14 pm, Zack Kitzmiller wrote:
> Sure thing Old code is Live.
>
> Feel free t
Do people not know that $("*").anything is very slow?
Yehuda Katz
Developer | Engine Yard
(ph) 718.877.1325
On Wed, Jan 13, 2010 at 2:16 PM, ajpiano wrote:
> The fact that $("*").bind() is WAY worse than $(document).bind()
> really ought to be shouted from the rooftops.
>
>
> On Jan 13, 11:46
@John
Thx a lot for the help, excellent service :)
On Jan 13, 8:16 pm, ajpiano wrote:
> The fact that $("*").bind() is WAY worse than $(document).bind()
> really ought to be shouted from the rooftops.
>
> On Jan 13, 11:46 am, John Resig wrote:
>
> > Well, before we had a very "non-silent" fai
> 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-
> var data = jQuery.extend(true, {}, arrComp);
You're extending an Array into an empty Object? That would lose the
Array-ness of the original object. I don't think this is a use case
that was ever anticipated, not sure it makes sense.
You could extend into an empty array [] to fix that, but after
Sure thing Old code is Live.
Feel free to take a look.
Zack
On Jan 13, 7:12 pm, Dave Methvin wrote:
> > After implementing the suggest fix (which does make more sense) this
> > issue is fixed.
>
> Zack, could you put up the old code with 1.4 on your site? I'd like to
> figure out why it did
Sure thing Old code is Live.
Feel free to take a look.
Zack
On Jan 13, 7:12 pm, Dave Methvin wrote:
> > After implementing the suggest fix (which does make more sense) this
> > issue is fixed.
>
> Zack, could you put up the old code with 1.4 on your site? I'd like to
> figure out why it did
> After implementing the suggest fix (which does make more sense) this
> issue is fixed.
Zack, could you put up the old code with 1.4 on your site? I'd like to
figure out why it didn't work.
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
After implementing the suggest fix (which does make more sense) this
issue is fixed.
Sloppy coding on my part, but did work as expected in 1.3
Thanks Guys.
On Jan 13, 5:47 pm, Zack Kitzmiller wrote:
> I've re-enabled 1.4, you can see, it doesn't work as one would
> expect.
>
> Zack
>
> On Jan 1
I've re-enabled 1.4, you can see, it doesn't work as one would
expect.
Zack
On Jan 12, 10:03 pm, Dave Methvin wrote:
> A test case would definitely help. It seems like the code should work
> as-is, but it's probably not quite doing what you expected.
>
> $("a[title!='']").click(function(
I've re-enabled 1.4, you can see, it doesn't work as one would
expect.
Zack
On Jan 12, 10:03 pm, Dave Methvin wrote:
> A test case would definitely help. It seems like the code should work
> as-is, but it's probably not quite doing what you expected.
>
> $("a[title!='']").click(function(
I updated the ticket. I'm not sure why you're getting a 403 error.
That's weird. I'll look into that further.
ref ticket #5795
http://dev.jquery.com/ticket/5795
On Jan 13, 12:43 pm, Karl Swedberg wrote:
> Hi there,
>
> I wasn't able to find a problem running the Star Rating plugin with
> 1.
The fact that $("*").bind() is WAY worse than $(document).bind()
really ought to be shouted from the rooftops.
On Jan 13, 11:46 am, John Resig wrote:
> Well, before we had a very "non-silent" failure - and that was causing
> his, and others, applications to break. I'm a firm believer that good
>
Well, before we had a very "non-silent" failure - and that was causing
his, and others, applications to break. I'm a firm believer that good
documentation is a proper anecdote to silence (hence the API docs are
updated to mention this change in 1.4 and it'll be in the release
notes).
--John
On We
@John : your patience has no limits ...
Although "silent failures" are a "big no-no" in computing, since
primordial times ?
Nice and fresh text :
http://partnerteamblog.shavlik.com/2009/09/02/the-silent-failure-that-leads-to-the-destruction-of-the-system/
And something *much* closer to jQuery us
A test case would definitely help. It seems like the code should work
as-is, but it's probably not quite doing what you expected.
$("a[title!='']").click(function() {
...
}).ajaxStart(function() {
$("#loader").show();
}).ajaxComplete(function() {
On Tue, Jan 12, 2010 at 4:46 PM, blizzard wrote:
> got it. that works perfectly now. will this be fixed in the final
> version?
Confirmed. I don't get the error either.
Great work, John!
-- Scott
--
You received this message because you are subscribed to the Google Groups
"jQuery Develop
Cool.
Interesting that is doesn't show up in XP.
On Jan 12, 1:52 pm, John Resig wrote:
> Hiya -
>
> I was able to replicate it on vista and windows 7 but not on xp - it's
> a very strange bug indeed and unfortunately one that'll require a lot
> of work to fix properly. I definitely plan on tack
Hiya -
I was able to replicate it on vista and windows 7 but not on xp - it's
a very strange bug indeed and unfortunately one that'll require a lot
of work to fix properly. I definitely plan on tackling this soon after
1.4 is out.
--John
On Tue, Jan 12, 2010 at 4:48 PM, Geoffrey wrote:
> **Fr
Yep, I just landed it:
http://github.com/jquery/jquery/commit/61983cbf176c599687c36ffbf4b64ae8697486a3
--John
On Tue, Jan 12, 2010 at 4:46 PM, blizzard wrote:
> got it. that works perfectly now. will this be fixed in the final
> version?
>
>
>
> On Jan 12, 2:56 pm, John Resig wrote:
>> Oh,
**Friendly bump...
I don't want to see this bug get overlooked. It is obscure, but when
it pops up, it hurts bad.
I see that you could not repicate this at
http://ejohn.org/files/bugs/inline/IE8_visible_after_inline.html
I replicated this on 4 different machines running vista and win 7.
Can any
got it. that works perfectly now. will this be fixed in the final
version?
On Jan 12, 2:56 pm, John Resig wrote:
> Oh, ok - that helps to clear some things up. Try
> this:http://ejohn.org/files/tmp-jq14-abort-2.js
>
> --John
>
>
>
> On Tue, Jan 12, 2010 at 3:42 PM, blizzard wrote:
> > Ok, I
> Makes sense to me. Would be good to mention in the api docs for live
> the substitute events for non-bubbling dom events; as of right now
> the api docs state "As of jQuery 1.4, the .live() method supports
> custom events as well as all JavaScript events." Thanks again for all
> the great work
Makes sense to me. Would be good to mention in the api docs for live
the substitute events for non-bubbling dom events; as of right now
the api docs state "As of jQuery 1.4, the .live() method supports
custom events as well as all JavaScript events." Thanks again for all
the great work on 1.4!
Oh, ok - that helps to clear some things up. Try this:
http://ejohn.org/files/tmp-jq14-abort-2.js
--John
On Tue, Jan 12, 2010 at 3:42 PM, blizzard wrote:
> Ok, I updated the script. Now is says that xhr is null at line 4970.
>
>
> On Jan 12, 2:39 pm, John Resig wrote:
>> Since I'm having tro
On Tue, Jan 12, 2010 at 3:42 PM, blizzard wrote:
> Ok, I updated the script. Now is says that xhr is null at line 4970.
Ditto.
-- Scott
--
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to jquery-...@go
Ok, I updated the script. Now is says that xhr is null at line 4970.
On Jan 12, 2:39 pm, John Resig wrote:
> Since I'm having trouble reproducing the problem can you let me know
> what happens when you use this copy of jQuery 1.4rc1
> instead?http://ejohn.org/files/tmp-jq14-abort.js
>
> Thanks
Since I'm having trouble reproducing the problem can you let me know
what happens when you use this copy of jQuery 1.4rc1 instead?
http://ejohn.org/files/tmp-jq14-abort.js
Thanks.
--John
On Tue, Jan 12, 2010 at 3:22 PM, blizzard wrote:
> Thank you Scott, that's exactly what I'm seeing.
>
>
>
Thank you Scott, that's exactly what I'm seeing.
On Jan 12, 2:13 pm, Scott Sauyet wrote:
> On Tue, Jan 12, 2010 at 2:53 PM, blizzard wrote:
> > I tried this on Windows 7 and on Windows 2003 server
>
> I just posted a screenshot confirming the error,
>
> http://dev.jquery.com/attachment/tick
On Tue, Jan 12, 2010 at 2:53 PM, blizzard wrote:
> I tried this on Windows 7 and on Windows 2003 server
I just posted a screenshot confirming the error,
http://dev.jquery.com/attachment/ticket/5788/screenshot_scott_sauyet_2010-01-12a.png
I get no error unless Firebug is open.
This consis
I tried this on Windows 7 and on Windows 2003 server
Here's the 1.4rc1 file that I'm using:
http://www.realestatehomepages.com/includes/cachablescripts/js/jquery/1.4rc1/jquery.js
On Jan 12, 1:44 pm, DBJDBJ wrote:
> @blizzard : where is your rc1 coming from ? what OS are you on ?
>
> On Jan 12
@blizzard : where is your rc1 coming from ? what OS are you on ?
On Jan 12, 7:22 pm, blizzard wrote:
> I promise I'm not going crazy. I just tried it on IE and Safari, same
> thing, then I tried it on another computer - same time.
>
> Any ideas?
>
> On Jan 12, 1:10 pm, John Resig wrote:
>
>
>
>
I promise I'm not going crazy. I just tried it on IE and Safari, same
thing, then I tried it on another computer - same time.
Any ideas?
On Jan 12, 1:10 pm, John Resig wrote:
> I just did exactly what you said (typed it in, got the validation
> message, tabbed down, tabbed back, entered the ri
I just did exactly what you said (typed it in, got the validation
message, tabbed down, tabbed back, entered the right email address)
but the validation message went away once I entered a correct email
address.
--John
On Tue, Jan 12, 2010 at 2:06 PM, blizzard wrote:
> yea, I just tried it agai
yea, I just tried it again. I typed in deckb...@q then tabbed down
then tabbed back and put in deckb...@quantumsite.com and it won't
clear the failed validation.
On Jan 12, 1:03 pm, blizzard wrote:
> If I put in something like deckberg then tab to the password, at this
> point it failed validat
If I put in something like deckberg then tab to the password, at this
point it failed validation once, then tab back and put in a correct
email and tab to the password it won't clear the failed validation.
so I can't submit the form.
On Jan 12, 12:54 pm, John Resig wrote:
> I'm having a hard tim
On Dec 22, 1:05 am, John Resig wrote:
> Just to clarify then, since jQuery already covers cases 2-4 as you're
> expecting it to and case #1 currently fails - and that case is
> decidedly not what this thread discussion started as.
I'm just pointing out several test cases that should be handled
co
John,
I think that this is a very common way to set the selection, and might
end up breaking people's code when they upgrade to jQuery 1.4. People
probably figured out that you could set the selection with either
property and used this in their code. When these people upgrade to
jQuery 1.4, thei
Just to clarify then, since jQuery already covers cases 2-4 as you're
expecting it to and case #1 currently fails - and that case is
decidedly not what this thread discussion started as.
> Consider the following cases:
>
> #1)
>
> Dummy
> Empty
>
>
> $('#x').val('')
> should select the second
On Dec 21, 10:32 pm, John Resig wrote:
> > Agreed, the change is broken! Wasn't there a test case for the above
> > scenario?
> The previous technique was definitely not the right one to use. Cases
> were coming up where the same string was being used for the value and
> the text in different plac
>> I can see why this optimization was done, but I think that this will
>> cause problems for a lot of people!
>
> Agreed, the change is broken! Wasn't there a test case for the above
> scenario?
The previous technique was definitely not the right one to use. Cases
were coming up where the same st
On Dec 21, 9:21 pm, Devon Govett wrote:
> I have found a bug in the jQuery.val() function.
> ...
> to the following in jQuery 1.4:
> this.selected = jQuery.inArray( this.value || this.text, values ) >= 0;
Indeed, this is a (probably unnoticed) change in logic.
Consider this:
Dummy
Empt
Might be worth re-opening http://dev.jquery.com/ticket/5459
On Dec 21, 7:22 am, weepy wrote:
> Calling animate with empty hash prevents that element from animating
> again
>
> $("#piece_1").animate({top:200}) => moves
>
> $("#piece_1").animate({}) => nothing happens (as expected)
>
> $("#piece_1
Awesome!
Thanks!
Devon
On Dec 16, 10:23 pm, John Resig wrote:
> Thanks for the test case, this is actually already fixed and in the
> latest nightly:http://code.jquery.com/jquery-nightly.js
>
> --John
>
>
>
> On Wed, Dec 16, 2009 at 9:54 PM, Devon Govett wrote:
> > Hello,
>
> > I have found a b
Looking at the example I suspect that it's due to some sort of weird
styling/CSS issue in IE. I'll have to investigate more in order to determine
exactly what the set of circumstances is that causes the issue. I'll try to
check in on it again before 1.4 and provide a definitive answer one way or
an
The ticket is titled "Slide Effects With IE6/IE7 Lists," and the
description is as follows:
slideUp, slideDown functions don't reveal/hide properly on lists in
IE6/IE7, while they work fine in other browsers (e.g. Firefox).
Applicable to list items (li) within unordered (ul) or ordered (ol)
lists.
Couldn't you do:
if(!!$(ele).attr('disabled')) {
//stuff
}
-- dz
On Thu, Aug 27, 2009 at 1:15 PM, William Chang wrote:
>
> Hey Matt,
> I understand now. Thanks!
>
> So, how do you avoid using attr() when you need to check for an
> attribute in the element? And, getting the value from an
On Aug 27, 11:16 am, William Chang wrote:
> I don't think the attribute is defined by default, after I did some
> more testing. I find the value return is not consistent between
> Firefox and IE8 (and probably previous versions of Microsoft Internet
> Explorer).
First of all, the attr() function
Hey Matt,
I understand now. Thanks!
So, how do you avoid using attr() when you need to check for an
attribute in the element? And, getting the value from an attribute?
Sincerely,
William Chang
http://www.williamchang.org
http://www.babybluebox.com
On Aug 27, 12:24 pm, Matt Kruse wrote:
> On Au
I don't think the attribute is defined by default, after I did some
more testing. I find the value return is not consistent between
Firefox and IE8 (and probably previous versions of Microsoft Internet
Explorer).
Please do this simple test with a page that has jQuery and then input
the console of
I don't think it is a bug. I'd rather think you've tried with
attributes that are defined by default.
To take your example, "disabled" attribute exists for html elements
and is equal to false by default, so it is normal that it'll return
false rather than undefined.
Regards
Ludovic
--~--~--
This should be posted to the jQuery UI list.
http://groups.google.com/group/jquery-ui
--John
On Thu, Aug 13, 2009 at 8:42 AM, ARZ wrote:
>
> Hi
> I found a very big bug in jquery ui 1.7.2
> please run this code and see what happend:
>
>
> ///
.css("display") == "none" would probably do the trick, as well.
--John
On Wed, Aug 12, 2009 at 8:40 PM, juuntu wrote:
>
> Is there an alternative for .is(':hidden') until this fix goes
> through?
>
> On Jul 23, 10:23 am, John Resig wrote:
> > Ok, I think this is a pretty simple tweak (since w
Is there an alternative for .is(':hidden') until this fix goes
through?
On Jul 23, 10:23 am, John Resig wrote:
> Ok, I think this is a pretty simple tweak (since we already look for the
> case of 'tr' which has the same problem, in IE). Just wanted to make sure it
> wasn't already covered. I've
Unfortunately I haven't had a chance to look in to this yet, but thanks for
your reduction - it'll certainly help!
--John
On Tue, Aug 11, 2009 at 1:55 PM, glyphobet wrote:
>
> I have confirmed that this is happening for other people in the IRC
> channel, and added some more information to the
I have confirmed that this is happening for other people in the IRC
channel, and added some more information to the bug report. Most
importantly, this bug is not present in Internet Explorer 8 running in
Internet Explorer 7 developer mode, only in the real Internet Explorer
7.
http://dev.jquery.c
Your suggestion doesn't work for me Andrea.
If I write $('.test:not(.test:first)').hide(); both elements become
visible in all the browsers I have tested (FF3.5, IE8, Safari
3.2.1-3.2.2).
Kindly,
Marcus
On 5 Aug, 14:42, Andrea Giammarchi
wrote:
> John,
> there is a problem with filters in IE.
John,
there is a problem with filters in IE.
I guess it is from missed getElementsByClassName support cause that
preFilter:CLASS is not performed elsewhere.
In few words, when there is a :not you work over 10 elements in the filter
rather than 2.
You can spot it adding a check inthe filter first
Yep, same code with just Sizzle and
onload = function(){
alert(Sizzle('.test:not(:first)', document).length);
};
produce 2 in IE and Safari 3, hope this help. I could investigate more if
necessary.
Regards
On Wed, Aug 5, 2009 at 1:23 PM, Andrea Giammarchi <
andrea.giammar...@
apparently the same happens with IE ... I guess it is Sizzle problem. length
2 for IE and Safari 3, 1 for FF 3.5, Chrome 2, Safari 4, Opera 10
On Wed, Aug 5, 2009 at 12:58 PM, smurkas wrote:
>
> Hello again John. I am not sure about the best way of posting a
> minimal test case but I put one up
Hello again John. I am not sure about the best way of posting a
minimal test case but I put one up on pastebin on this address:
http://pastebin.com/m4a61f583
The page only contains two divs with the same class and the selector
code I wrote above. Works in Firefox 3.5 but not in Safari 3.2.1-3.2.2
Not a known bug that I know of. Do you have a test case that we can use to
reproduce?
--John
On Mon, Aug 3, 2009 at 6:11 PM, smurkas wrote:
>
> Hello.
>
> While developing a site for a client I made a page where I hid all the
> div:s with the class news_container like this
> $('.news_container
It could be an Employee monitor, if behind an intranet, or some
warm/anti-virus with some injected stuff by default.
Use the same script with a blank page and one single input or simply shot
the DOM via
Ok, I think this is a pretty simple tweak (since we already look for the
case of 'tr' which has the same problem, in IE). Just wanted to make sure it
wasn't already covered. I've added it to my todo list.
--John
On Thu, Jul 23, 2009 at 2:12 PM, arno_schaefer wrote:
>
> On Jul 23, 7:32 pm, John
On Jul 23, 7:32 pm, John Resig wrote:
> Out of curiosity, does the latest jQuery nightly fix
> this?http://code.jquery.com/jquery-nightly.js
Nope, already tried that.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Out of curiosity, does the latest jQuery nightly fix this?
http://code.jquery.com/jquery-nightly.js
--John
On Thu, Jul 23, 2009 at 11:45 AM, Arno Schäfer wrote:
>
> Hi,
>
> I am experiencing a bug (IMHO) with the :hidden selector in IE. Here is
> my sample code:
>
>
> $(function () {
>
> I checked no plugin is installed for IE 6.0
> Did you check on Windows 2000 Professional.
>
I don't have access to that operating system.
I'm still leaning towards some sort of external modification going on since
there's really no reason for another element to appear when there isn't one
on th
I checked no plugin is installed for IE 6.0
Did you check on Windows 2000 Professional.
Regards,
Chirag
On Wed, Jul 22, 2009 at 7:13 PM, John Resig wrote:
> I'm almost wondering if you have some plugin/proxy installed that's
> affecting the content of your page.
>
> --John
>
>
>
> On Wed, Jul 2
I'm almost wondering if you have some plugin/proxy installed that's
affecting the content of your page.
--John
On Wed, Jul 22, 2009 at 6:24 AM, Chirag Patel wrote:
> Thanks for your quick answer. I accessed your link.
> This time both length and size() gives me the same result but incorrect
>
I am using jQuery v1.3.1.
On Wed, Jul 22, 2009 at 3:54 PM, Chirag Patel wrote:
> Thanks for your quick answer. I accessed your link.
> This time both length and size() gives me the same result but incorrect
> count 4.
> There are only three elements with attribute "name" butI still get 4
> count
Thanks for your quick answer. I accessed your link.
This time both length and size() gives me the same result but incorrect
count 4.
There are only three elements with attribute "name" butI still get 4 count.
However, the same works fine in IE 7 & 8.
Please note that I have IE 6.0.* installed on Wi
Using your demo page I'm getting '3' for both .length and .size() in IE 6
and in Firefox.
http://ejohn.org/files/bugs/name-attr/
--John
On Tue, Jul 21, 2009 at 9:25 AM, Chirag wrote:
>
> Hello,
>
> Recently when I was doing some testing, I found issue with length
> property. The size() method
Yes! The current nightly seems to work as expected. Thanks.
-Pete
On Jul 15, 2009, at 3:45 PM, John Resig wrote:
> Pete -
>
> Does it work with the jQuery nightlies? We made some tweaks to
> how :hidden/:visible worked in 1.3 and have since made some more
> changes to hopefully fix bugs.
>
Pete -
Does it work with the jQuery nightlies? We made some tweaks to how
:hidden/:visible worked in 1.3 and have since made some more changes to
hopefully fix bugs.
http://code.jquery.com/jquery-nightly.js
--John
On Wed, Jul 15, 2009 at 3:28 PM, Pete Schwamb wrote:
>
> I just spent a few hou
I just spent a few hours tracking this down as well, and I'd guess
there are others out there hitting the same issue (http://
groups.google.com/group/jquery-en/browse_thread/thread/
3d81f54b111c1408?fwc=1).
This does appear to work as expected in older builds (1.2.x). How was
it working there?
Good catch - and thanks for the patch! I just landed the improvement:
http://dev.jquery.com/ticket/4884
I made one minor tweak to the patch: In the case where .attr("name",
function(){}) occurs the jQuery.isFunction(value) check is cached (rather
than occurring at every iteration in the array).
T
On Jun 4, 6:55 pm, Jeff wrote:
> I'm not certain if you can truly consider this a bug but I thought I'd
> post it anyway. I learned that some of the built-in effects don't
> work properly when non-floated parent contains floated children.
> Specifically, slideUp, fadeOut, and toggle do nothing i
I don't think so - I've updated the documentation to be a little more
precise.
http://docs.jquery.com/Attributes/val
--John
On Tue, May 26, 2009 at 3:26 PM, Alex Farcas wrote:
>
> I noticed val() ignores the 'value' attribute on html elements.
>
> If i have this markup:
> < div id="test" value
One more bump!
On Sat, Apr 4, 2009 at 9:13 PM, Maniquí wrote:
> Hi all.
>
> This bug seems to affect just IE6/7. So fire it up if you want to do
> some quick testing :)
>
> == Testing environments ==
>
> - Working version (jQuery 1.2.6 + jQuery ScrollTo 1.4.1 +
> jQuery.localScroll 1.2.7):
>
> h
Hey Josh,
Thanks for clearing that up!
Luke
On May 3, 10:48 am, Josh Powell wrote:
> You are right, it has to do with setTimeout. In IE, setTimeout does
> not allow you to pass parameters like this, and in fact it is against
> the spec to do so.
>
> http://www.claws-and-paws.com/node/1252
>
You are right, it has to do with setTimeout. In IE, setTimeout does
not allow you to pass parameters like this, and in fact it is against
the spec to do so.
http://www.claws-and-paws.com/node/1252
On May 3, 12:34 am, Luke Bayes wrote:
> Hey Josh,
>
> Thanks so much for taking the time to go
Hey Josh,
Thanks so much for taking the time to go through this. You are
absolutely right in that I didn't test my distilled example - Sorry
about that!
I dug a little deeper, and it seems my problem is somehow related to
IE's handling of setTimeout. As I said, I'm working with Google Maps
and o
I tested the code you gave, and it worked fine in IE7. I got
one
two
three
four
I'm suspecting that you've distilled the example down from some real
code (good practice!) and it was the real code that wasn't working
and you didn't test the distilled code. I suspect that in the real
code, this
On Thu, Apr 23, 2009 at 10:16 PM, Brandon Aaron wrote:
> I think the test pages are broken, maybe missing some styles/js?
Oh, yes, sorry, I've disabled the styles/javascript just to show something
to a client.
They are enabled again.
You can test the pages.
Thanks!
--~--~-~--~~
I think the test pages are broken, maybe missing some styles/js?
--
Brandon Aaron
On Sat, Apr 4, 2009 at 7:13 PM, Maniquí wrote:
>
> Hi all.
>
> This bug seems to affect just IE6/7. So fire it up if you want to do
> some quick testing :)
>
> == Testing environments ==
>
> - Working version (jQue
Bump! :)
--
Ariel Flesler
On Apr 4, 9:13 pm, Maniquí wrote:
> Hi all.
>
> This bug seems to affect just IE6/7. So fire it up if you want to do
> some quick testing :)
>
> == Testing environments ==
>
> - Working version (jQuery 1.2.6 + jQuery ScrollTo 1.4.1 +
> jQuery.localScroll 1.2.7):
>
> ht
It makes no difference at all.
Could it be an issue related to selectors (and not strictly related to
animate()) only affecting Webkit?
It seems like the animation is being run "properly" but not to the proper
DOM element.
Instead the animation seems to be applied to first child of the animated
el
Instead of animating to {"width":"0px"} what happens if you animate to
{"width":"hide"} (you can remove the callback then, as well).
--John
On Sun, Apr 5, 2009 at 12:10 AM, Julián Landerreche wrote:
>
> Hi John,
> thanks for your quick reply.
>
> I've tested with the nightly build, but it see
Hi John,
thanks for your quick reply.
I've tested with the nightly build, but it seems the issue is still
there.
You can check it here:
http://test.rudysmusic.com/electric-guitars/new/?jquery=1.3.2-nightly
If there is something else I can do, don't hesitate to ask me. Also,
I'm currently on #jq
Could you test with a nightly? It's likely that this was already fixed.
http://code.jquery.com/nightlies/jquery-2009-03-26.js
--John
On Sat, Apr 4, 2009 at 11:38 PM, Julián Landerreche wrote:
>
> Hi again,
>
> this bug seems to affect just Webkit (Safari/Chrome) browsers.
> The thing have bee
Thanks Fabio !
It works back after removing those lines from:
http://code.jquery.com/nightlies/jquery-2009-03-26.js
*** jquery-2009-03-26.js.orig 2009-03-30 19:43:31.0 +0200
--- jquery-2009-03-26.js2009-03-30 19:45:50.0 +0200
***
*** 1459,1468
f
Hi John,
I think this is a problem with the sibling optimization I made. It
fails when the searched element is in the checkSet.
In dirNode and dirNodeCheck the following if:
if ( sibDir && elem.nodeType === 1 ) {
elem.sizcache = doneName;
Actually, I think this one was already fixed.
Can you test it real quick?
http://code.jquery.com/nightlies/jquery-2009-03-26.js
--John
On Mon, Mar 30, 2009 at 8:24 AM, yodza wrote:
>
> Hi,
>
> From 1.3.1 to 1.3.2 sibling selector does not work anymore:
> http://jquery.nodnod.net/cases/277
>
Two working patches attached to the bug, either a closure or a
new .rawCss function. .I can't change the "Needs:" on the bug.
There's a little bit of discussion in the bug on other things, but
they're fairly unrelated to what is actually being fixed.
On Mar 4, 3:58 pm, Daniel Friesen wrote:
> Fi
Filed: http://dev.jquery.com/ticket/4295
I'll consider writing a patch later on while on the train.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com]
-Nadir-Point & Wiki-Tools (http://nadir-point.com) (http://wiki-tools.com)
-MonkeyScript (http://monkeyscript.org)
-Animepedi
Sounds reasonable. You should file a bug with this information attached:
http://dev.jquery.com/newticket
--John
On Wed, Mar 4, 2009 at 6:21 PM, Daniel Friesen
wrote:
>
> I just did a little check after noticing something while developing. But
> .css('margin'); and .css('padding'); are fairly
Actually, it might be attributable to an old jquery library? The site
we are working on has jquery 1.2.6 (just noticed, sorry).
All of the browsers return the defined height or max-height as inner /
outer height, none are returning the equivalent of the scrollHeight (I
am not sure if this was th
1 - 100 of 131 matches
Mail list logo
