Not sure what I did but it seems to be working now. Thanks for your
help.
On Feb 17, 12:07 pm, John Resig wrote:
> We'll definitely need a page that we can look at because I'm not able
> to duplicate this.
> --John
>
> On Tue, Feb 17, 2009 at 3:04 PM, matanich wrote:
>
> > I have tried the foll
Perhaps the documentation should also be fixed to note that .append
actually accepts multiple arguments to append, not just one.
One of the comments in that ticket was that he could not use:
var form = $( '' ); form.append(
$( "'
).text('true') ) .after(
$( "'
).text('false') )
Out of curiosity, what does jQuery do in this case? Does it silently
fail, die on error because it tried to use a property from a nonexistant
parent, or output an explicit error slapping the author for using
something that can't be done?
If it's a silent fail, it might be nice for this edge cas
Yeah, this is really just a documentation issue. Do you want to just
tweak the docs for those entries and be sure to mention that they
require that the element(s) are already inserted in to a document or
another node?
--John
On Tue, Feb 17, 2009 at 10:59 PM, Dave Methvin wrote:
>
> The before
The before/after/insertBefore/insertAfter methods require a parentNode
so that the content can be inserted relative to the element. So, $
("unusual").after("case") will fail.
http://dev.jquery.com/ticket/3940
Maybe that should just be documented? There are plenty of other ways
to solve the probl
This wasn't the case very recently - it's was actually *just*
resolved. I'll close it.
--John
On Tue, Feb 17, 2009 at 8:45 PM, Dave Methvin wrote:
>
> So in the case like $("div").find("a") where an a element can be
> reached via multiple descendants, should the duplicates be removed? I
> exp
Can you link to a relatively simple test page? There is probably
something else going on that isn't clear from the snippets.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this
I saw your ticket,
http://dev.jquery.com/ticket/4174
it looks like it may be a duplicate of this one:
http://dev.jquery.com/ticket/4161
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
So in the case like $("div").find("a") where an a element can be
reached via multiple descendants, should the duplicates be removed? I
expected they would be.
http://dev.jquery.com/ticket/2490
--~--~-~--~~~---~--~~
You received this message because you are subscr
Mike,
I am happy to see some of the questions/points you make above were
already answered here:
http://groups.google.com/group/jquery-dev/browse_thread/thread/ddb5387f309e8b60/905344e61030b9ca?lnk=gst&q=event+delegation+document+order#905344e61030b9ca
At that time, I was answered that "document
thanks!
On Tue, Feb 17, 2009 at 4:56 PM, John Resig wrote:
>
> Thanks Chris - just landed this fix.
>
> --John
>
>
>
> On Tue, Feb 17, 2009 at 4:41 PM, chris thatcher
> wrote:
> > If your unlucky enough to have to develop on a windows machine you might
> get
> > errors when running the unit tes
Thanks Chris - just landed this fix.
--John
On Tue, Feb 17, 2009 at 4:41 PM, chris thatcher
wrote:
> If your unlucky enough to have to develop on a windows machine you might get
> errors when running the unit tests in rhino with the UTF-8 selectors.
>
> I resolved this in 1.2.6 and 1.3.1 by m
If your unlucky enough to have to develop on a windows machine you might get
errors when running the unit tests in rhino with the UTF-8 selectors.
I resolved this in 1.2.6 and 1.3.1 by modifying the Makefile to use
JAR = java -Dfile.encoding=utf-8 -jar ${BUILD_DIR}/js.jar
Thanks!
--
Christophe
I took a few minutes to go back and look at this and realized that of
course the test suite fails. I have changed the expected behavior off
of which the tests are based. The new code allows "live" events to
bubble (which in my opinion is the correct behavior). In order to
cancel that behavior, the
We'll definitely need a page that we can look at because I'm not able
to duplicate this.
--John
On Tue, Feb 17, 2009 at 3:04 PM, matanich wrote:
>
> I have tried the following and they all do the same fade speed. Any
> other suggestions?
>
> .fadeOut(2000)
> .fadeOut('2000')
> .fadeOut("2000")
I have tried the following and they all do the same fade speed. Any
other suggestions?
.fadeOut(2000)
.fadeOut('2000')
.fadeOut("2000")
.fadeOut('slow')
.fadeOut('fast')
Thanks
On Feb 13, 5:54 am, John Resig wrote:
> If you put in a number, don't put it in a string - just leave it as a number
I ended up just removing the indexOf code in favor of using ranges -
seems to work well!
--John
On Tue, Feb 17, 2009 at 2:59 AM, Robert Katić wrote:
>
> To ensure order and uniqueness with XML and non current documents too,
> we have to ensure that the NodeList "allSort" is the correct one.
>
I just tested and it's working again after some of the recent changes:
http://jsbin.com/ajuja
Thanks for the test case!
--John
On Tue, Feb 17, 2009 at 12:11 PM, Nikola wrote:
>
> I tried out a few things with 1.3.2pre and noticed that the Dialog
> window doesn't open in MSIE. Here's a Dialo
I tried out a few things with 1.3.2pre and noticed that the Dialog
window doesn't open in MSIE. Here's a Dialog test case from an
example Richard put together in the UI group.
http://jsbin.com/anota/edit
On Feb 16, 7:58 pm, dmiFedorenko wrote:
> I check 1.3.2a on my php cms (js/ajax/some jPlug
This is going to have to wait for 1.3.3 - 1.3.2 is already frozen and
almost out the door.
--John
On Tue, Feb 17, 2009 at 11:19 AM, mike.helgeson wrote:
>
> No it does not pass the test suite. I think the problem is from the
> bubbling in "trigger"...
> Any chance of getting this method added
No it does not pass the test suite. I think the problem is from the
bubbling in "trigger"...
Any chance of getting this method added for 1.3.2? else, the
"liveConvert" function moved to the jQuery namespace?
jQuery.fn.delegate = function( type, selector, fn ){
var proxy = jQuery.event.proxy( f
I just created a ticket (http://dev.jquery.com/ticket/4174) with demo/
test-cases for both versions of jQuery...
---
The following code produces quite different results in jQuery 1.2.6
and 1.3.1 ...
var protoElm = $('#proto b');
protoElm
.bind(
Hello, first time poster on this group. Joined specifically because I have
hit a wall with this problem and though I can work around it, I would still
like to find a resolution.
I have a page where users can create new tabs. At the bottom I have a hidden
div that I clone into each new tab the user
I check 1.3.2a on my php cms (js/ajax/some jPlugins) with firefox
3.0.6 & selenium (about 950 commands) - no issues :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group
Interesting work, Mike. I'll take a deeper look at it after 1.3.2
lands. Out of curiosity - did you test this against the live tests in
the jQuery test suite?
--John
On Mon, Feb 16, 2009 at 6:05 PM, mike.helgeson wrote:
>
> - The selector must be run, before the event handler is bound... this
Yep - it's on my todo list for the next release!
--John
On Tue, Feb 17, 2009 at 12:33 AM, ajpiano wrote:
>
> With the advent of native JSON support in browsers forthcoming, should
> jQuery.support check for the existence of the JSON obj and use it as
> the preferred way of parsing JSON whenev
a small bug, i guess you've noticed it already:
the second for loop on Line 3800 in show method should be outside of
the first for loop.
i found this, when trying to show a group of initialy hidden nodes (it
would show only the first one)
or am I missing something?
/Matas
On Feb 17, 2:23 am, J
Fixed at http://dev.jquery.com/changeset/6216
--
Ariel Flesler
http://flesler.blogspot.com
On Jan 31, 2:05 pm, Jörn Zaefferer
wrote:
> Okay, thanks for clarifying, Ariel.
>
> Jörn
>
> On Sat, Jan 31, 2009 at 1:02 PM, Ariel Flesler wrote:
>
> > No, currentTarget was a 1.3.x addition. I added it
Re the following code :
>$(".grid").bind('click', function(ev) {
> var sq = $(ev.target).closest('.sq');
> ...
>
>});
Would make sense to support this with live by specifying the parent
element (".grid") in this case?
I.e. the above could be written something like this:
$(".sq").live("click",
I founded an error in my code.
Instead of
array.splice(i--, 1);
goes
array.splice(i, 1);
On Feb 17, 8:59 am, Robert Katić wrote:
> To ensure order and uniqueness with XML and non current documents too,
> we have to ensure that the NodeList "allSort" is the correct one.
> Maybe something l
30 matches
Mail list logo
