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 jere...@gmail.com wrote:
I'm
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 tylerwor...@gmail.com wrote:
If I put in something like deckberg then tab to the password, at this
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 tylerwor...@gmail.com wrote:
yea,
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 jere...@gmail.com wrote:
I just did exactly what you said (typed it in, got the validation
message, tabbed down, tabbed
@blizzard : where is your rc1 coming from ? what OS are you on ?
On Jan 12, 7:22 pm, blizzard tylerwor...@gmail.com 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
On Jan 11, 2010, at Jan 11,7:15 PM , Nikita Vasilyev wrote:
Is there any example of using QUnit with Rhino (or another JS engine)?
(at least without DOM)
I would like to run QUnit tests from Rake task.
I run qunit tests with the SpiderMonkey/Ruby/Johnson port of env.js. All the
pieces are
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 dbj...@gmail.com wrote:
@blizzard : where is your rc1 coming from ? what OS are you on
On Tue, Jan 12, 2010 at 2:53 PM, blizzard tylerwor...@gmail.com 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
Thank you Scott, that's exactly what I'm seeing.
On Jan 12, 2:13 pm, Scott Sauyet scott.sau...@gmail.com wrote:
On Tue, Jan 12, 2010 at 2:53 PM, blizzard tylerwor...@gmail.com wrote:
I tried this on Windows 7 and on Windows 2003 server
I just posted a screenshot confirming the error,
Just tried using JQuery 1.4RC1 with Slimbox and after clicking on an
image and
allowing it to expand, the whole page gets darker just before the text
appears
below the image. This doesn't happen with 1.3.
--
You received this message because you are subscribed to the Google Groups
jQuery
Binding to the focus and blur events using the live methods appears to
not be functional in 1.4rc1. Looks like a ticket was opened (http://
dev.jquery.com/ticket/5689) for 1.4a2 but I can confirm this is still
an issue with 1.4rc1.
Link to test case:
http://jquery-test.110mb.com/
--
You
Hi,
I had a look at Jquery 1.4 RC and found that code :
line 3170 :
return;
window.Sizzle = Sizzle;
I think that the second line is not very usefull (but not a bug)
Thomas.
PS : to be honest, closure compiler helped me a bit
--
You received this message because you are subscribed to the
Tested http://dev.jquery.com/ticket/5700 in 1.4rc1 and it's still
behaving weird in IE8, but I guess it's a sizzle bug?
Best regards,
Matias
--
You received this message because you are subscribed to the Google Groups
jQuery Development group.
To post to this group, send email to
.ajaxComplete doesn't work?
I have some code that works fine with 1.3.2, but doesn't seems to
fire .ajaxComplete() in 1.4, Maybe I missed something.
You can find the offending code at http://ampc.org/convention. The
loader div doesn't hide when ajax is finished.
--
You received this message
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 tylerwor...@gmail.com wrote:
Thank you Scott, that's exactly
Ok, I updated the script. Now is says that xhr is null at line 4970.
On Jan 12, 2:39 pm, John Resig jere...@gmail.com 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
On Tue, Jan 12, 2010 at 3:42 PM, blizzard tylerwor...@gmail.com 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
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 tylerwor...@gmail.com wrote:
Ok, I updated the script. Now is says that xhr is null at line 4970.
On Jan 12, 2:39 pm, John Resig
That has always been in there - we'll probably end up tweaking our
build script to just remove it but for the time-being it's not hurting
anything.
--John
On Tue, Jan 12, 2010 at 1:28 PM, TomaP pia...@gmail.com wrote:
Hi,
I had a look at Jquery 1.4 RC and found that code :
line 3170 :
Mark,
I am sorry but with all the other bugs and tasks John needs to get done
before launch can you please host an example so John doesn't have to do all
that? It would really save some time for him to be able to look at your
problem.
Thanks for understanding.
Ralph
On Tue, Jan 12, 2010 at
got it. that works perfectly now. will this be fixed in the final
version?
On Jan 12, 2:56 pm, John Resig jere...@gmail.com 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
**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
Never mind. Here is the one with 1.3.2:
http://test.learningjquery.com/slimbox/example.html
And here is the one with 1.4rc1:
http://test.learningjquery.com/slimbox/example-1.4.html
Looks like #lbOverlay is being inserted in the wrong place with
1.4rc1. Haven't looked at the code yet, so
I notice that jQuery.isEmptyObject() in 1.4rc1 uses an unfiltered
for...in, so it'll pick up on inherited properties. Is this
intentional? Is so, maybe it should be documented or there should be a
flag on isEmptyObject() to only look at the object's own properties.
--
You received this message
Yep, I just landed it:
http://github.com/jquery/jquery/commit/61983cbf176c599687c36ffbf4b64ae8697486a3
--John
On Tue, Jan 12, 2010 at 4:46 PM, blizzard tylerwor...@gmail.com wrote:
got it. that works perfectly now. will this be fixed in the final
version?
On Jan 12, 2:56 pm, John Resig
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
Cool.
Interesting that is doesn't show up in XP.
On Jan 12, 1:52 pm, John Resig jere...@gmail.com 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
It was intentional in that in the places where we use it we weren't
concerned with properties bleeding through from prototypes. I will
make a note of it in the documentation and we can re-examine this
after 1.4 is out.
http://api.jquery.com/jQuery.isEmptyObject/
--John
On Tue, Jan 12, 2010 at
Thanks Karl.
On Tue, Jan 12, 2010 at 4:51 PM, Karl Swedberg k...@englishrules.comwrote:
Never mind. Here is the one with 1.3.2:
http://test.learningjquery.com/slimbox/example.html
And here is the one with 1.4rc1:
http://test.learningjquery.com/slimbox/example-1.4.html
Looks like
Thanks. I do realize that in the vast majority of cases unfiltered is
fine, but as a convenience method it'd be nice to be able to filter.
On Tue, Jan 12, 2010 at 4:55 PM, John Resig jere...@gmail.com wrote:
It was intentional in that in the places where we use it we weren't
concerned with
I noticed that you commented out the 1.4 script on your test page -
could you perhaps make a reduced test case that I can take a look at?
I would greatly appreciate it.
--John
On Tue, Jan 12, 2010 at 12:03 PM, Zack Kitzmiller
zackkitzmil...@gmail.com wrote:
.ajaxComplete doesn't work?
I
On Tue, Jan 12, 2010 at 4:46 PM, blizzard tylerwor...@gmail.com 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
Okay, I reduced the code to the part that is producing the problem
(there is still some cruft in there, but I gotta run). It looks like
the issue has to do with changes in the .add() method. I must say that
the manner of element insertion used by the plugin author is rather
unconventional.
Looks like the new $.extend implementation doesn't let you recursively
extend a function anymore:
// create function w/properties
var T = $.test = function() { alert(T.prop ? 'good' : 'bad'); };
$.extend(T, { prop: false });
// elsewhere, do deep configuration
$.extend(true, $, {
test: {
This was an intentional change. We found that when doing a deep extend
on non-objects (and I mean that in the plain object and plain
array sense) a lot of unexpected behavior was encountered. We only
deep extend plain objects and plain arrays now (those that match
jQuery.isPlainObject or
Thanks for the quick answer and good explanation, John! I had not
thought about the many types of objects (natives, nodes, etc) where
this would certainly be weird and problematic. Limiting this seems
quite sensible.
Though, because one further argument will be a lot less work for me
than
@Nathan: you just landed yourself a task ;o) Why don't you write
functionExtend() plugin ?
--
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,
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() {
Just landed some code that'll likely fix the issue:
http://github.com/jquery/jquery/commit/5d49335eace4311de890b871e057d8b6e9122eb6
This was actually something that I wanted to fix a little while ago
and forgot about.
--John
On Tue, Jan 12, 2010 at 5:37 PM, Karl Swedberg k...@englishrules.com
I'm not sure if a fix for it will land before 1.4, unfortunately,
although I will make an attempt to fix it soon after.
And just to clarify: It looks like this issue is in the current
version of jQuery (1.3.2) as well, per the test case.
--John
On Tue, Jan 12, 2010 at 11:52 AM, matiasnu
Never heard of sending a body with a DELETE. Reading more it doesn't
seem like something that you should really rely upon:
http://stackoverflow.com/questions/299628/is-an-entity-body-allowed-for-an-http-delete-request
That being said the fix was really quite simple:
41 matches
Mail list logo
