[jquery-dev] Re: The ~ selector broken in 1.3.2 but works in nightly and 1.3.1

2009-03-06 Thread d3r1v3d (Gavin Mulligan)

Actually, I found a bit more time to actually attempt the 'patch' I
suggested in the previous post. I want to tweak my suggestion to:

1.3.2 jquery.js:
- 2357: match = checkSet[elem.sizset];
+ 2357: match = true;

That fixes the error found in the test code given in the root of this
list thread, however I have no idea what the far-reaching implications
of that change are in the grand scheme of jQuery. :)

- Gavin

On Mar 6, 9:37 am, "d3r1v3d (Gavin Mulligan)" 
wrote:
> I did a bit of snooping and think I've tracked down what the problem
> seems to be. In selector.js, I believe the issues emanates from
> changes made to the dirCheck function.
>
> In 1.3.2, the match variable is set to the 'elem.sizset' index of the
> checkSet array. This checkSet array contains the 'selector validation
> status' (my terminology) of a series of sibling divs (in this case).
> The following code, in 1.3.2 dirCheck(...), should set the match
> variable equal to the element which matches the given selector based
> on the current element in checkSet being investigated:
> if ( elem.sizcache === doneName ) {
>     match = checkSet[elem.sizset];
>     break;
>
> }
>
> In the test file, the div in checkSet being investigated is the second
> div in the body and elem, in this case, is the div#prev which matches
> to the given selector. I believe that match should be set equal to
> elem here instead of checkSet[elem.sizset] or, in other words:
> - match = checkSet[elem.sizSet];
> + match = elem;
>
> This is similar to how 1.3.1 handles this case. However, I am nowhere
> near familiar enough with the selector code to suggest this as a
> definitive patch. Does someone who is intimately familiar with the
> selector.js code think this would do the trick?
>
> - Gavin
>
> On Mar 6, 8:32 am, Cloudream  wrote:
>
> > nightly is 1.3.1 ...
>
> > On Fri, Mar 6, 2009 at 1:30 PM, Igor  wrote:
>
> > > Hi!
> > > Have been using your library for ages, it is awesome, thank you!
>
> > > Recently found some issues, that seems to be related to
> > > previousSibling ( "~" ) selector
> > > Can you point me to a place, where it is broken, since i afraid of
> > > using nightly builds in product
>
> > > Sample markup:
> > > 
> > > 
> > > 
> > > http://ajax.googleapis.com/ajax/</a>
> > > libs/jquery/1.3.2/jquery.min.js">
> > >  
> > > 
> > >        $(document).ready(function(){
> > >                console.log($('#prev ~ div').length);/*expecting 1, got 
> > > zero
> > > in
> > > 1.3.2*/
> > >        });
> > > 
> > > 
> > > 
> > >        1
> > >        2
> > > 
> > > 
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: The ~ selector broken in 1.3.2 but works in nightly and 1.3.1

2009-03-06 Thread d3r1v3d (Gavin Mulligan)

I did a bit of snooping and think I've tracked down what the problem
seems to be. In selector.js, I believe the issues emanates from
changes made to the dirCheck function.

In 1.3.2, the match variable is set to the 'elem.sizset' index of the
checkSet array. This checkSet array contains the 'selector validation
status' (my terminology) of a series of sibling divs (in this case).
The following code, in 1.3.2 dirCheck(...), should set the match
variable equal to the element which matches the given selector based
on the current element in checkSet being investigated:
if ( elem.sizcache === doneName ) {
match = checkSet[elem.sizset];
break;
}

In the test file, the div in checkSet being investigated is the second
div in the body and elem, in this case, is the div#prev which matches
to the given selector. I believe that match should be set equal to
elem here instead of checkSet[elem.sizset] or, in other words:
- match = checkSet[elem.sizSet];
+ match = elem;

This is similar to how 1.3.1 handles this case. However, I am nowhere
near familiar enough with the selector code to suggest this as a
definitive patch. Does someone who is intimately familiar with the
selector.js code think this would do the trick?

- Gavin

On Mar 6, 8:32 am, Cloudream  wrote:
> nightly is 1.3.1 ...
>
> On Fri, Mar 6, 2009 at 1:30 PM, Igor  wrote:
>
> > Hi!
> > Have been using your library for ages, it is awesome, thank you!
>
> > Recently found some issues, that seems to be related to
> > previousSibling ( "~" ) selector
> > Can you point me to a place, where it is broken, since i afraid of
> > using nightly builds in product
>
> > Sample markup:
> > 
> > 
> > 
> > http://ajax.googleapis.com/ajax/
> > libs/jquery/1.3.2/jquery.min.js">
> >  
> > 
> >        $(document).ready(function(){
> >                console.log($('#prev ~ div').length);/*expecting 1, got zero
> > in
> > 1.3.2*/
> >        });
> > 
> > 
> > 
> >        1
> >        2
> > 
> > 
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: ajaxStart() question / suggestion

2009-03-06 Thread d3r1v3d (Gavin Mulligan)

After looking at in the $.ajax(...) function, which is implicitly
invoked via $.load(...), I noticed that the 'ajaxStart' event is
triggered explicitly using jQuery.event.trigger(...). Therefore, I
don't think the event is triggered on a specific element (which would
obviously allow you to access it via 'this').

However, I see a number of solutions which might fit the bill for you
application. Have you thought of using the new Event.live(...)
functionality (http://docs.jquery.com/Events/live)? You could include
something similar to the following code:

$('button.ajax').live('click', function(){
var $loadTarget = $(this);
$loadTarget.css(
top: $loadTarget.offset().top,
left: $loadTarget.offset().left,
width: $loadTarget.width(),
height: $loadTarget.height()
).show();

   // ajax stuff here
});

Every button inserted into your page DOM with the class 'ajax' would
have this click handler bound to them. You could get fancier by
including attributes such as ajaxURL="..." to these buttons and having
the click handler invoke the Ajax call using each button's specific
URL.

Just an idea.

- Gavin

On Mar 6, 6:20 am, Alexandre Plennevaux  wrote:
> i know, i have no problem to make my script work if i specifically
> tweak my load() calls but i would like to set it in one place.
>
> See:  http://pixeline.be/test/loadanim/demo.html
>
> The buttons use the same div, shape it to the same size as the load
> container and display it. i would like to automate that behaviour
> instead of having to attach it to all 'click' events.
>
> On Fri, Mar 6, 2009 at 12:09 PM, d3r1v3d (Gavin Mulligan)
>
>  wrote:
>
> > For the throbber div you mentioned, why not initialize it just before
> > you make the call to load()? As the name suggests, all Ajax calls are
> > asynchronous, so you could initialize the throbber div to start
> > displaying 'Loading... Please Wait' just before you make the call and
> > then hide this loading notification div in the success function
> > attached to the Ajax call.
>
> > Hope this helps.
>
> > - Gavin
>
> > On Mar 6, 5:59 am, pixeline  wrote:
> >> Hello,
>
> >> I'm trying to set a function that should be triggered on all ajax
> >> start events. Therefore i thought i should use
>
> >> $.ajaxStart(myFunc);
>
> >> What my function should do is overlay the specific DOM element that
> >> will receive the new content with a throbber, "please wait" div,
> >> typically the element against which load() is called. yet i can't find
> >> a way to get it from inside the function.
>
> >> Suggestion: shouldn't the target element be stored in the ajax
> >> object ?
>
> >> I've posted on hte general jquery for answers before posting it here 
> >> :http://groups.google.com/group/jquery-en/browse_thread/thread/df7f42a...
>
> >> Feel free to reply there if you think my suggestion is not relevant.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: ajaxStart() question / suggestion

2009-03-06 Thread d3r1v3d (Gavin Mulligan)

For the throbber div you mentioned, why not initialize it just before
you make the call to load()? As the name suggests, all Ajax calls are
asynchronous, so you could initialize the throbber div to start
displaying 'Loading... Please Wait' just before you make the call and
then hide this loading notification div in the success function
attached to the Ajax call.

Hope this helps.

- Gavin

On Mar 6, 5:59 am, pixeline  wrote:
> Hello,
>
> I'm trying to set a function that should be triggered on all ajax
> start events. Therefore i thought i should use
>
> $.ajaxStart(myFunc);
>
> What my function should do is overlay the specific DOM element that
> will receive the new content with a throbber, "please wait" div,
> typically the element against which load() is called. yet i can't find
> a way to get it from inside the function.
>
> Suggestion: shouldn't the target element be stored in the ajax
> object ?
>
> I've posted on hte general jquery for answers before posting it here 
> :http://groups.google.com/group/jquery-en/browse_thread/thread/df7f42a...
>
> Feel free to reply there if you think my suggestion is not relevant.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: Test external css is applied to current document.

2009-03-04 Thread d3r1v3d (Gavin Mulligan)

There is a function called hasClass() that you can apply to the
results of a selector (http://docs.jquery.com/Attributes/hasClass). Do
you think this fits with what you're looking for?

For example, let's say you have HTML like so:
test

You could query whether this div has the class 'test' applied by
writing:
$('div#someDiv').hasClass('test')

- Gavin

On Mar 4, 8:38 pm, Code  wrote:
> Is there’s a CSSApplied event that I can listen to if my javascript
> code relies on CSS properties?
>
> For example:
> In an external css file I define a css class:
> .test
> {
>   width:100px;
>   height: 100px;
>
> }
>
> Then in html document I have an element test.
> Later also in this document I try to get the dimension of the the div
> element.
> But if the css is not applied, I got a dimension other than
> 100X100px.
> Wonder is there any way to detect all css classes is applied?
>
> Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: (Ticket #3808) ajax: $().load() fails 404 if there is a hash in the url

2009-03-04 Thread d3r1v3d (Gavin Mulligan)

I've updated the ticket with both the test files and the proposed
patch to resolve it. (http://dev.jquery.com/ticket/3808)

The patch includes spicyj's suggested code with a minor tweak. In
Javascript, string.replace(...) does not edit the string it operates
on, but merely returns a copy with the suggested changes. As such, I
set the result equal to the string being operated upon by the search-
and-replace regular expression.

Cheers.

- Gavin

On Mar 3, 9:51 pm, "d3r1v3d (Gavin Mulligan)" 
wrote:
> Having said that, I just realized what you were saying and you're
> absolutely right, spicyj. Fragments (or anchors, as I called them) go
> at the end, according to the official W3C spec (http://www.w3.org/TR/
> WD-html40-970708/htmlweb.html). So, your patch is superior to mine. :)
>
> - Gavin
>
> On Mar 3, 9:47 pm, "d3r1v3d (Gavin Mulligan)" 
> wrote:
>
> > In the code I suggested, I attempt to match on a '?' to see if a query
> > string is present. If so, the regular expression grabs all URL
> > segments starting with '#' and ending with '?' and replaces them with
> > '?'. Otherwise, the other branch yanks everything from the '#'
> > onwards.
>
> > I wanted to keep the query string intact since I figured some people
> > might prefer to craft GET request URLs and insert their data directly
> > into the query string instead of putting it in the data parameter. Not
> > something I'd do, but didn't want to break anything. :)
>
> > - Gavin
>
> > On Mar 3, 9:01 pm, spicyj  wrote:
>
> > > Doesn't the fragment go after the query string?
>
> > > Assuming that's right, here's a patch that's a bit simpler:
>
> > >http://pastie.org/406716
>
> > > ~spicyj
>
> > > On Mar 3, 5:48 pm, "d3r1v3d (Gavin Mulligan)" 
> > > wrote:
>
> > > > Hey John,
>
> > > > Sorry I'm not at my machine with SVN access or I'd provide a diff of
> > > > my proposed change for fixing this.
>
> > > > In (http://dev.jquery.com/browser/trunk/jquery/src/ajax.js), within
> > > > the ajax method (starting line 174), I'd recommend adding the
> > > > following lines:
>
> > > > // START
> > > > if (s.url.match(/\?/))
> > > > {
> > > >     s.url.replace(/#(.*)?\?/g, '?'));}
>
> > > > else
> > > > {
> > > >     s.url.replace(/#(.*)?/g, '');}
>
> > > > // END
>
> > > > Essentially, this yanks any anchor tag from a given URL while
> > > > preserving the query string (if one exists). Additionally, an if block
> > > > could be placed around this code to do an initial match for hash marks
> > > > (#) to test for the existence of anchors in the first place, I just
> > > > left it out since it seemed a tad excessive. Hope this helps.
>
> > > > - Gavin
>
> > > > On Mar 3, 4:46 pm, John Resig  wrote:
>
> > > > > Hey Gavin -
>
> > > > > Thanks for the fact-finding, that definitely clears things up - I'll
> > > > > see if I can fix this for 1.3.3.
>
> > > > > --John
>
> > > > > On Tue, Mar 3, 2009 at 4:40 PM, d3r1v3d (Gavin Mulligan)
>
> > > > >  wrote:
>
> > > > > > For kicks, I've been looking into the causes behind the problem this
> > > > > > ticket poses. I've managed to duplicate the error in the test script
> > > > > > that the ticket poster provided (http://pixeline.be/experiments/
> > > > > > jquerybeta/test2.html).
>
> > > > > > Essentially, the problem is that Ajax GET requests (haven't tried 
> > > > > > with
> > > > > > POST) to a URL which happens to include an anchor ('#') consistently
> > > > > > fail with HTTP 404 status errors (Document Not Found) in Internet
> > > > > > Explorer (tested with 7.0.5730.13), while these same requests are
> > > > > > processed just fine in Firefox 3, Chrome, et al.
>
> > > > > > After putzing around a bit, I noticed something interesting. When I
> > > > > > ran the test case in Internet Explorer, my Apache error log 
> > > > > > displayed
> > > > > > the following error:
> > > > > > [Tue Mar 03 15:59:30 2009] [error] [client ***.**.**.**] File does 
> > > > > > not
> > > > > >

[jquery-dev] Re: (Ticket #3808) ajax: $().load() fails 404 if there is a hash in the url

2009-03-03 Thread d3r1v3d (Gavin Mulligan)

Having said that, I just realized what you were saying and you're
absolutely right, spicyj. Fragments (or anchors, as I called them) go
at the end, according to the official W3C spec (http://www.w3.org/TR/
WD-html40-970708/htmlweb.html). So, your patch is superior to mine. :)

- Gavin

On Mar 3, 9:47 pm, "d3r1v3d (Gavin Mulligan)" 
wrote:
> In the code I suggested, I attempt to match on a '?' to see if a query
> string is present. If so, the regular expression grabs all URL
> segments starting with '#' and ending with '?' and replaces them with
> '?'. Otherwise, the other branch yanks everything from the '#'
> onwards.
>
> I wanted to keep the query string intact since I figured some people
> might prefer to craft GET request URLs and insert their data directly
> into the query string instead of putting it in the data parameter. Not
> something I'd do, but didn't want to break anything. :)
>
> - Gavin
>
> On Mar 3, 9:01 pm, spicyj  wrote:
>
> > Doesn't the fragment go after the query string?
>
> > Assuming that's right, here's a patch that's a bit simpler:
>
> >http://pastie.org/406716
>
> > ~spicyj
>
> > On Mar 3, 5:48 pm, "d3r1v3d (Gavin Mulligan)" 
> > wrote:
>
> > > Hey John,
>
> > > Sorry I'm not at my machine with SVN access or I'd provide a diff of
> > > my proposed change for fixing this.
>
> > > In (http://dev.jquery.com/browser/trunk/jquery/src/ajax.js), within
> > > the ajax method (starting line 174), I'd recommend adding the
> > > following lines:
>
> > > // START
> > > if (s.url.match(/\?/))
> > > {
> > >     s.url.replace(/#(.*)?\?/g, '?'));}
>
> > > else
> > > {
> > >     s.url.replace(/#(.*)?/g, '');}
>
> > > // END
>
> > > Essentially, this yanks any anchor tag from a given URL while
> > > preserving the query string (if one exists). Additionally, an if block
> > > could be placed around this code to do an initial match for hash marks
> > > (#) to test for the existence of anchors in the first place, I just
> > > left it out since it seemed a tad excessive. Hope this helps.
>
> > > - Gavin
>
> > > On Mar 3, 4:46 pm, John Resig  wrote:
>
> > > > Hey Gavin -
>
> > > > Thanks for the fact-finding, that definitely clears things up - I'll
> > > > see if I can fix this for 1.3.3.
>
> > > > --John
>
> > > > On Tue, Mar 3, 2009 at 4:40 PM, d3r1v3d (Gavin Mulligan)
>
> > > >  wrote:
>
> > > > > For kicks, I've been looking into the causes behind the problem this
> > > > > ticket poses. I've managed to duplicate the error in the test script
> > > > > that the ticket poster provided (http://pixeline.be/experiments/
> > > > > jquerybeta/test2.html).
>
> > > > > Essentially, the problem is that Ajax GET requests (haven't tried with
> > > > > POST) to a URL which happens to include an anchor ('#') consistently
> > > > > fail with HTTP 404 status errors (Document Not Found) in Internet
> > > > > Explorer (tested with 7.0.5730.13), while these same requests are
> > > > > processed just fine in Firefox 3, Chrome, et al.
>
> > > > > After putzing around a bit, I noticed something interesting. When I
> > > > > ran the test case in Internet Explorer, my Apache error log displayed
> > > > > the following error:
> > > > > [Tue Mar 03 15:59:30 2009] [error] [client ***.**.**.**] File does not
> > > > > exist: //dummy.html#love, referer: ...
>
> > > > > I did not get this error with the other browsers that successfully
> > > > > execute the call to load().
>
> > > > > Case in point, it seems that, with the IE ajax request, the anchor
> > > > > (and anchor name) is not correctly parsed out of the base document's
> > > > > file name when it is served. This would be akin to a web server
> > > > > receiving a get request for webPage.html with parameters foo=bar and
> > > > > searching for a document on the local file-system named '/apache/
> > > > > htdocs/webPage.html?foo=bar'. Obviously any query strings (or in this
> > > > > case, anchor data) should be removed from the URL before this point.
>
> > > > > I would argue, however, that these anchors have no place in Ajax
> > > > > requests to begin with, as the entire dummy.html document will be
> > > > > retrieved and returned in the Ajax response, thus eliminating the need
> > > > > for an anchor tag. However, I would propose that the jQuery Ajax
> > > > > component could be extended to parse out any erroneous anchor tags
> > > > > from request URLs so that this is no longer a problem in the future.
>
> > > > > - Gavin
>
> > > > > (I apologize if I seem overly verbose, just want to get the facts out)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: (Ticket #3808) ajax: $().load() fails 404 if there is a hash in the url

2009-03-03 Thread d3r1v3d (Gavin Mulligan)

In the code I suggested, I attempt to match on a '?' to see if a query
string is present. If so, the regular expression grabs all URL
segments starting with '#' and ending with '?' and replaces them with
'?'. Otherwise, the other branch yanks everything from the '#'
onwards.

I wanted to keep the query string intact since I figured some people
might prefer to craft GET request URLs and insert their data directly
into the query string instead of putting it in the data parameter. Not
something I'd do, but didn't want to break anything. :)

- Gavin

On Mar 3, 9:01 pm, spicyj  wrote:
> Doesn't the fragment go after the query string?
>
> Assuming that's right, here's a patch that's a bit simpler:
>
> http://pastie.org/406716
>
> ~spicyj
>
> On Mar 3, 5:48 pm, "d3r1v3d (Gavin Mulligan)" 
> wrote:
>
> > Hey John,
>
> > Sorry I'm not at my machine with SVN access or I'd provide a diff of
> > my proposed change for fixing this.
>
> > In (http://dev.jquery.com/browser/trunk/jquery/src/ajax.js), within
> > the ajax method (starting line 174), I'd recommend adding the
> > following lines:
>
> > // START
> > if (s.url.match(/\?/))
> > {
> >     s.url.replace(/#(.*)?\?/g, '?'));}
>
> > else
> > {
> >     s.url.replace(/#(.*)?/g, '');}
>
> > // END
>
> > Essentially, this yanks any anchor tag from a given URL while
> > preserving the query string (if one exists). Additionally, an if block
> > could be placed around this code to do an initial match for hash marks
> > (#) to test for the existence of anchors in the first place, I just
> > left it out since it seemed a tad excessive. Hope this helps.
>
> > - Gavin
>
> > On Mar 3, 4:46 pm, John Resig  wrote:
>
> > > Hey Gavin -
>
> > > Thanks for the fact-finding, that definitely clears things up - I'll
> > > see if I can fix this for 1.3.3.
>
> > > --John
>
> > > On Tue, Mar 3, 2009 at 4:40 PM, d3r1v3d (Gavin Mulligan)
>
> > >  wrote:
>
> > > > For kicks, I've been looking into the causes behind the problem this
> > > > ticket poses. I've managed to duplicate the error in the test script
> > > > that the ticket poster provided (http://pixeline.be/experiments/
> > > > jquerybeta/test2.html).
>
> > > > Essentially, the problem is that Ajax GET requests (haven't tried with
> > > > POST) to a URL which happens to include an anchor ('#') consistently
> > > > fail with HTTP 404 status errors (Document Not Found) in Internet
> > > > Explorer (tested with 7.0.5730.13), while these same requests are
> > > > processed just fine in Firefox 3, Chrome, et al.
>
> > > > After putzing around a bit, I noticed something interesting. When I
> > > > ran the test case in Internet Explorer, my Apache error log displayed
> > > > the following error:
> > > > [Tue Mar 03 15:59:30 2009] [error] [client ***.**.**.**] File does not
> > > > exist: //dummy.html#love, referer: ...
>
> > > > I did not get this error with the other browsers that successfully
> > > > execute the call to load().
>
> > > > Case in point, it seems that, with the IE ajax request, the anchor
> > > > (and anchor name) is not correctly parsed out of the base document's
> > > > file name when it is served. This would be akin to a web server
> > > > receiving a get request for webPage.html with parameters foo=bar and
> > > > searching for a document on the local file-system named '/apache/
> > > > htdocs/webPage.html?foo=bar'. Obviously any query strings (or in this
> > > > case, anchor data) should be removed from the URL before this point.
>
> > > > I would argue, however, that these anchors have no place in Ajax
> > > > requests to begin with, as the entire dummy.html document will be
> > > > retrieved and returned in the Ajax response, thus eliminating the need
> > > > for an anchor tag. However, I would propose that the jQuery Ajax
> > > > component could be extended to parse out any erroneous anchor tags
> > > > from request URLs so that this is no longer a problem in the future.
>
> > > > - Gavin
>
> > > > (I apologize if I seem overly verbose, just want to get the facts out)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: (Ticket #3808) ajax: $().load() fails 404 if there is a hash in the url

2009-03-03 Thread d3r1v3d (Gavin Mulligan)

Hey John,

Sorry I'm not at my machine with SVN access or I'd provide a diff of
my proposed change for fixing this.

In (http://dev.jquery.com/browser/trunk/jquery/src/ajax.js), within
the ajax method (starting line 174), I'd recommend adding the
following lines:

// START
if (s.url.match(/\?/))
{
s.url.replace(/#(.*)?\?/g, '?'));
}
else
{
s.url.replace(/#(.*)?/g, '');
}
// END

Essentially, this yanks any anchor tag from a given URL while
preserving the query string (if one exists). Additionally, an if block
could be placed around this code to do an initial match for hash marks
(#) to test for the existence of anchors in the first place, I just
left it out since it seemed a tad excessive. Hope this helps.

- Gavin

On Mar 3, 4:46 pm, John Resig  wrote:
> Hey Gavin -
>
> Thanks for the fact-finding, that definitely clears things up - I'll
> see if I can fix this for 1.3.3.
>
> --John
>
> On Tue, Mar 3, 2009 at 4:40 PM, d3r1v3d (Gavin Mulligan)
>
>  wrote:
>
> > For kicks, I've been looking into the causes behind the problem this
> > ticket poses. I've managed to duplicate the error in the test script
> > that the ticket poster provided (http://pixeline.be/experiments/
> > jquerybeta/test2.html).
>
> > Essentially, the problem is that Ajax GET requests (haven't tried with
> > POST) to a URL which happens to include an anchor ('#') consistently
> > fail with HTTP 404 status errors (Document Not Found) in Internet
> > Explorer (tested with 7.0.5730.13), while these same requests are
> > processed just fine in Firefox 3, Chrome, et al.
>
> > After putzing around a bit, I noticed something interesting. When I
> > ran the test case in Internet Explorer, my Apache error log displayed
> > the following error:
> > [Tue Mar 03 15:59:30 2009] [error] [client ***.**.**.**] File does not
> > exist: //dummy.html#love, referer: ...
>
> > I did not get this error with the other browsers that successfully
> > execute the call to load().
>
> > Case in point, it seems that, with the IE ajax request, the anchor
> > (and anchor name) is not correctly parsed out of the base document's
> > file name when it is served. This would be akin to a web server
> > receiving a get request for webPage.html with parameters foo=bar and
> > searching for a document on the local file-system named '/apache/
> > htdocs/webPage.html?foo=bar'. Obviously any query strings (or in this
> > case, anchor data) should be removed from the URL before this point.
>
> > I would argue, however, that these anchors have no place in Ajax
> > requests to begin with, as the entire dummy.html document will be
> > retrieved and returned in the Ajax response, thus eliminating the need
> > for an anchor tag. However, I would propose that the jQuery Ajax
> > component could be extended to parse out any erroneous anchor tags
> > from request URLs so that this is no longer a problem in the future.
>
> > - Gavin
>
> > (I apologize if I seem overly verbose, just want to get the facts out)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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] (Ticket #3808) ajax: $().load() fails 404 if there is a hash in the url

2009-03-03 Thread d3r1v3d (Gavin Mulligan)

For kicks, I've been looking into the causes behind the problem this
ticket poses. I've managed to duplicate the error in the test script
that the ticket poster provided (http://pixeline.be/experiments/
jquerybeta/test2.html).

Essentially, the problem is that Ajax GET requests (haven't tried with
POST) to a URL which happens to include an anchor ('#') consistently
fail with HTTP 404 status errors (Document Not Found) in Internet
Explorer (tested with 7.0.5730.13), while these same requests are
processed just fine in Firefox 3, Chrome, et al.

After putzing around a bit, I noticed something interesting. When I
ran the test case in Internet Explorer, my Apache error log displayed
the following error:
[Tue Mar 03 15:59:30 2009] [error] [client ***.**.**.**] File does not
exist: //dummy.html#love, referer: ...

I did not get this error with the other browsers that successfully
execute the call to load().

Case in point, it seems that, with the IE ajax request, the anchor
(and anchor name) is not correctly parsed out of the base document's
file name when it is served. This would be akin to a web server
receiving a get request for webPage.html with parameters foo=bar and
searching for a document on the local file-system named '/apache/
htdocs/webPage.html?foo=bar'. Obviously any query strings (or in this
case, anchor data) should be removed from the URL before this point.

I would argue, however, that these anchors have no place in Ajax
requests to begin with, as the entire dummy.html document will be
retrieved and returned in the Ajax response, thus eliminating the need
for an anchor tag. However, I would propose that the jQuery Ajax
component could be extended to parse out any erroneous anchor tags
from request URLs so that this is no longer a problem in the future.

- Gavin

(I apologize if I seem overly verbose, just want to get the facts out)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: Is it possible to get mouse position when the page has loaded without moving the mouse?

2009-02-27 Thread d3r1v3d (Gavin Mulligan)

Hi Abel,

I think it's more of a problem as to when the browsers update the
appropriate DOM elements that determine the user's current mouse
position (e.g. pageX / pageY and clientX / clientY). We can use jQuery
(or really just POJS) to trigger code that runs when a document is
loaded, but if these DOM elements aren't initialized, they'll always
return 0.

- Gavin

On Feb 27, 6:50 pm, Abel K  wrote:
> I am sorry, I am very new at the entire jQuery thing, but isn't there a
> ready() function that could trigger the mouse cursor position? In Flash,
> this would not even be a thing to be thinking about, let alone an
> cross-browser compatibility issue...
>
> Cordially,
> Abel K.www.worldkit.com
>
> On Fri, Feb 27, 2009 at 6:42 PM, Andrea Giammarchi <
>
> andrea.giammar...@gmail.com> wrote:
> > I bet is the classic banner, spot, or JS effect to attach to the mouse and
> > somebody asked him why it is not attached since the beginning ... well,
> > Marcus, if it is the case tell them that the browser is inside a window and
> > if the user is not interacting with that window there's nothing you can do
> > via web except create a plugin to download, even more disturbing ;-)
>
> > In every other case, I am curios as well  but thanks to this issue I
> > discovered that onmouseover in internet explorer isfired ONLY if the
> > document.body is already present in the DOM, somwthing that could be useful
> > for the doScroll interception as well (since Diego is reading this post)
>
> > On Fri, Feb 27, 2009 at 11:13 PM, d3r1v3d (Gavin Mulligan) <
> > vtga...@gmail.com> wrote:
>
> >> Just out of curiosity, Marcus, I would be interested to know why you
> >> want to know the user's mouse position before they move it. Maybe
> >> there's a better solution that'll fit snugly within the scope of your
> >> requirements.
>
> >> - Gavin
>
> >> On Feb 27, 12:02 pm, unwiredbrain  wrote:
> >> > 2009/2/27 d3r1v3d (Gavin Mulligan) :
>
> >> > > You're right, it does seem to work in IE 7. However, it still fails to
> >> > > work in Firefox and Chrome...
>
> >> > Both methods suggested by Andrea Giammarchi are working properly on my
> >> > box -- Firefox 3.0.6, Linux.
>
> >> > I wonder if it's just a Windows' window focus management issue...
> >> > Mac OS X testing anyone?
>
> >> > Hope that helps
> >> > --
> >> > unwiredbrain
> >> > Linux user #437712
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: Is it possible to get mouse position when the page has loaded without moving the mouse?

2009-02-27 Thread d3r1v3d (Gavin Mulligan)

Just out of curiosity, Marcus, I would be interested to know why you
want to know the user's mouse position before they move it. Maybe
there's a better solution that'll fit snugly within the scope of your
requirements.

- Gavin

On Feb 27, 12:02 pm, unwiredbrain  wrote:
> 2009/2/27 d3r1v3d (Gavin Mulligan) :
>
> > You're right, it does seem to work in IE 7. However, it still fails to
> > work in Firefox and Chrome...
>
> Both methods suggested by Andrea Giammarchi are working properly on my
> box -- Firefox 3.0.6, Linux.
>
> I wonder if it's just a Windows' window focus management issue...
> Mac OS X testing anyone?
>
> Hope that helps
> --
> unwiredbrain
> Linux user #437712
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: Is it possible to get mouse position when the page has loaded without moving the mouse?

2009-02-27 Thread d3r1v3d (Gavin Mulligan)

You're right, it does seem to work in IE 7. However, it still fails to
work in Firefox and Chrome...

- Gavin

On Feb 27, 11:42 am, Andrea Giammarchi 
wrote:
> I tested in IE :D
>
> On Fri, Feb 27, 2009 at 2:20 PM, d3r1v3d (Gavin Mulligan) 
> > wrote:
>
> > Yep, I tried your code in a demo page and it confirmed my initial
> > suspicions. It works great when the DOM of the test page is
> > initialized with the mouse coordinates. However, this only happens
> > when the mouse is initially moved after the page is refreshed.
>
> > Put your mouse in the middle of the test page, and hit F5 without
> > moving your mouse. No alerts will pop up until your mouse moves at
> > least a pixel. If you continue slamming refresh, no alerts at all will
> > display. The 'mouseover' event doesn't trigger until the mouse is
> > moved over the body of the web page. Additionally, the same is true if
> > you use your mouse to manually hit the refresh button, since it exists
> > outside the confines of the page.
>
> > Note: I tested in Chrome and Firefox 3 on Windows.
>
> > - Gavin
>
> > On Feb 27, 8:47 am, Andrea Giammarchi 
> > wrote:
> > > I do not need to move the mouse to fire that event ... have you tried?
>
> > > write this wherever and press F5 without move the mouse ...
>
> > > document.documentElement.onmouseover = function(){
> > >     alert("Who moved?");
>
> > > };
>
> > > Regards
>
> > > On Fri, Feb 27, 2009 at 12:54 PM, d3r1v3d (Gavin Mulligan) <
>
> > > vtga...@gmail.com> wrote:
>
> > > > Yes, but that requires the 'mouseover' event to be executed; which, in
> > > > turn, requires that a user move their mouse over the page at least a
> > > > pixel for it to trigger.
>
> > > > I believe Marcus was asking if it was possible to retrieve a user's
> > > > current mouse position without moving the cursor at all.
>
> > > > - Gavin
>
> > > > On Feb 27, 4:17 am, Andrea Giammarchi 
> > > > wrote:
> > > > > $(document.documentElement).bind("mouseover", function(eventObj){
> > > > >     alert([eventObj.clientX, eventObj.clientY]);
>
> > > > > });
>
> > > > > On Thu, Feb 26, 2009 at 2:49 PM, d3r1v3d (Gavin Mulligan) <
> > > > vtga...@gmail.com
>
> > > > > > wrote:
>
> > > > > > Hi Marcus,
>
> > > > > > The function I've always used for obtaining the current mouse
> > position
> > > > > > is:
> > > > > > function getMousePosition(eventObj){
> > > > > >    if (eventObj.pageX && eventObj.pageY)
> > > > > >    {
> > > > > >        return {x: eventObj.pageX, y: eventObj.pageY};
> > > > > >    }
>
> > > > > >    return {x: (eventObj.clientX + document.body.scrollLeft -
> > > > > > document.body.clientLeft),
> > > > > >              y: (eventObj.clientY + document.body.scrollTop -
> > > > > > document.body.clientTop)};
> > > > > > }
>
> > > > > > However, the major caveat here is that you need to bind this
> > function
> > > > > > to some event. A given browser will keep track of mouse movements
> > > > > > within itself, but I do not believe it tracks movements outside its
> > > > > > window. Additionally, unless a user has moved their mouse within a
> > > > > > given web page, I don't believe the DOM for that page is updated
> > with
> > > > > > the appropriate coordinates. So, long story short, I don't think
> > what
> > > > > > you're asking is possible.
>
> > > > > > - Gavin
>
> > > > > > On Feb 26, 9:41 am, smurkas  wrote:
> > > > > > > Hello. I ran into this problem today. I would like to know the
> >  mouse
> > > > > > > position when  the page has loaded without the user having to
> >  move
> > > > > > > the mouse. I have tried just getting the  xy-values but it
> > returned
> > > > > > > undefined if I triggered on document load and 0 0 if I just
> > trigger
> > > > > > > different mouse events when  the page has loaded via firebug.
>
> > > > > > > Is it possible to  get the values without moving the  mouse and
> > if
> > > > so,
> > > > > > > how do I do it?
>
> > > > > > > Yours  kindly, Marcus.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: Is it possible to get mouse position when the page has loaded without moving the mouse?

2009-02-27 Thread d3r1v3d (Gavin Mulligan)

Yep, I tried your code in a demo page and it confirmed my initial
suspicions. It works great when the DOM of the test page is
initialized with the mouse coordinates. However, this only happens
when the mouse is initially moved after the page is refreshed.

Put your mouse in the middle of the test page, and hit F5 without
moving your mouse. No alerts will pop up until your mouse moves at
least a pixel. If you continue slamming refresh, no alerts at all will
display. The 'mouseover' event doesn't trigger until the mouse is
moved over the body of the web page. Additionally, the same is true if
you use your mouse to manually hit the refresh button, since it exists
outside the confines of the page.

Note: I tested in Chrome and Firefox 3 on Windows.

- Gavin

On Feb 27, 8:47 am, Andrea Giammarchi 
wrote:
> I do not need to move the mouse to fire that event ... have you tried?
>
> write this wherever and press F5 without move the mouse ...
>
> document.documentElement.onmouseover = function(){
>     alert("Who moved?");
>
> };
>
> Regards
>
> On Fri, Feb 27, 2009 at 12:54 PM, d3r1v3d (Gavin Mulligan) <
>
> vtga...@gmail.com> wrote:
>
> > Yes, but that requires the 'mouseover' event to be executed; which, in
> > turn, requires that a user move their mouse over the page at least a
> > pixel for it to trigger.
>
> > I believe Marcus was asking if it was possible to retrieve a user's
> > current mouse position without moving the cursor at all.
>
> > - Gavin
>
> > On Feb 27, 4:17 am, Andrea Giammarchi 
> > wrote:
> > > $(document.documentElement).bind("mouseover", function(eventObj){
> > >     alert([eventObj.clientX, eventObj.clientY]);
>
> > > });
>
> > > On Thu, Feb 26, 2009 at 2:49 PM, d3r1v3d (Gavin Mulligan) <
> > vtga...@gmail.com
>
> > > > wrote:
>
> > > > Hi Marcus,
>
> > > > The function I've always used for obtaining the current mouse position
> > > > is:
> > > > function getMousePosition(eventObj){
> > > >    if (eventObj.pageX && eventObj.pageY)
> > > >    {
> > > >        return {x: eventObj.pageX, y: eventObj.pageY};
> > > >    }
>
> > > >    return {x: (eventObj.clientX + document.body.scrollLeft -
> > > > document.body.clientLeft),
> > > >              y: (eventObj.clientY + document.body.scrollTop -
> > > > document.body.clientTop)};
> > > > }
>
> > > > However, the major caveat here is that you need to bind this function
> > > > to some event. A given browser will keep track of mouse movements
> > > > within itself, but I do not believe it tracks movements outside its
> > > > window. Additionally, unless a user has moved their mouse within a
> > > > given web page, I don't believe the DOM for that page is updated with
> > > > the appropriate coordinates. So, long story short, I don't think what
> > > > you're asking is possible.
>
> > > > - Gavin
>
> > > > On Feb 26, 9:41 am, smurkas  wrote:
> > > > > Hello. I ran into this problem today. I would like to know the  mouse
> > > > > position when  the page has loaded without the user having to  move
> > > > > the mouse. I have tried just getting the  xy-values but it returned
> > > > > undefined if I triggered on document load and 0 0 if I just trigger
> > > > > different mouse events when  the page has loaded via firebug.
>
> > > > > Is it possible to  get the values without moving the  mouse and if
> > so,
> > > > > how do I do it?
>
> > > > > Yours  kindly, Marcus.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: Is it possible to get mouse position when the page has loaded without moving the mouse?

2009-02-27 Thread d3r1v3d (Gavin Mulligan)

Yes, but that requires the 'mouseover' event to be executed; which, in
turn, requires that a user move their mouse over the page at least a
pixel for it to trigger.

I believe Marcus was asking if it was possible to retrieve a user's
current mouse position without moving the cursor at all.

- Gavin

On Feb 27, 4:17 am, Andrea Giammarchi 
wrote:
> $(document.documentElement).bind("mouseover", function(eventObj){
>     alert([eventObj.clientX, eventObj.clientY]);
>
> });
>
> On Thu, Feb 26, 2009 at 2:49 PM, d3r1v3d (Gavin Mulligan) 
> > wrote:
>
> > Hi Marcus,
>
> > The function I've always used for obtaining the current mouse position
> > is:
> > function getMousePosition(eventObj){
> >    if (eventObj.pageX && eventObj.pageY)
> >    {
> >        return {x: eventObj.pageX, y: eventObj.pageY};
> >    }
>
> >    return {x: (eventObj.clientX + document.body.scrollLeft -
> > document.body.clientLeft),
> >              y: (eventObj.clientY + document.body.scrollTop -
> > document.body.clientTop)};
> > }
>
> > However, the major caveat here is that you need to bind this function
> > to some event. A given browser will keep track of mouse movements
> > within itself, but I do not believe it tracks movements outside its
> > window. Additionally, unless a user has moved their mouse within a
> > given web page, I don't believe the DOM for that page is updated with
> > the appropriate coordinates. So, long story short, I don't think what
> > you're asking is possible.
>
> > - Gavin
>
> > On Feb 26, 9:41 am, smurkas  wrote:
> > > Hello. I ran into this problem today. I would like to know the  mouse
> > > position when  the page has loaded without the user having to  move
> > > the mouse. I have tried just getting the  xy-values but it returned
> > > undefined if I triggered on document load and 0 0 if I just trigger
> > > different mouse events when  the page has loaded via firebug.
>
> > > Is it possible to  get the values without moving the  mouse and if so,
> > > how do I do it?
>
> > > Yours  kindly, Marcus.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: .remove() without the event+data stripping

2009-02-26 Thread d3r1v3d (Gavin Mulligan)

However, if remove() is adequately documented in the jQuery API (as it
seems to be), then there should really be no confusion with comparing
it to removeChild()... Deprecation and aliasing is a quick path to API
bloat, IMO.

- Gavin

On Feb 26, 2:00 pm, Daniel Friesen  wrote:
> Renaming doesn't have to be done without backwards compatibility. Just
> alias the old .remove to the .destory and @deprecate .remove for new
> code so people don't get bitten anymore while old code still works.
>
> ~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)
> -Animepedia (http://anime.wikia.com)
> -Narutopedia (http://naruto.wikia.com)
> -Soul Eater Wiki (http://souleater.wikia.com)
>
> John Resig wrote:
> >> what I was trying to get flying was the idea of renaming of `.remove()
> >> ` to `.destroy()`, to remove the last trace of confusion
> >> with .removeChild()
>
> >> Does anybody have an opinion on that?
>
> > That's not happening. That will change a critical method of the jQuery
> > API - breaking thousands of jQuery sites.
>
> > --John
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: Is it possible to get mouse position when the page has loaded without moving the mouse?

2009-02-26 Thread d3r1v3d (Gavin Mulligan)

Hi Marcus,

The function I've always used for obtaining the current mouse position
is:
function getMousePosition(eventObj){
if (eventObj.pageX && eventObj.pageY)
{
return {x: eventObj.pageX, y: eventObj.pageY};
}

return {x: (eventObj.clientX + document.body.scrollLeft -
document.body.clientLeft),
  y: (eventObj.clientY + document.body.scrollTop -
document.body.clientTop)};
}

However, the major caveat here is that you need to bind this function
to some event. A given browser will keep track of mouse movements
within itself, but I do not believe it tracks movements outside its
window. Additionally, unless a user has moved their mouse within a
given web page, I don't believe the DOM for that page is updated with
the appropriate coordinates. So, long story short, I don't think what
you're asking is possible.

- Gavin

On Feb 26, 9:41 am, smurkas  wrote:
> Hello. I ran into this problem today. I would like to know the  mouse
> position when  the page has loaded without the user having to  move
> the mouse. I have tried just getting the  xy-values but it returned
> undefined if I triggered on document load and 0 0 if I just trigger
> different mouse events when  the page has loaded via firebug.
>
> Is it possible to  get the values without moving the  mouse and if so,
> how do I do it?
>
> Yours  kindly, Marcus.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: Cannot run test framework with fresh SVN checkout

2009-02-26 Thread d3r1v3d (Gavin Mulligan)

Just an update (for those who care). I tried building the minified
jQuery file from the base jquery.js generated from the Ant build using
the Makefile and it choked with the same syntax errors I was getting
when trying to build the same files with Ant. After cleaning out the
generated files and rebuilding the base jquery file with Make,
everything was gravy.

It definitely seems that there's a problem with the build.xml shipped
with the version of jQuery on the trunk. However, if the majority of
people are building with Make anyways, does it make sense to include
support for Ant builds when it's not maintained? Just curious.

Cheers.

- Gavin

On Feb 25, 5:59 pm, "d3r1v3d (Gavin Mulligan)" 
wrote:
> Alright, I'll just make do with Make then. Although, I'm curious if
> anyone else on the list running Linux and using Ant has run into the
> same problem.
>
> Thanks.
>
> - Gavin
>
> On Feb 25, 4:37 pm, John Resig  wrote:
>
> > Umm... I'm not seeing this problem, but then again I'm using the Makefile.
>
> > Also, runtest is pretty outdated at his point. That project is being
> > maintained over here now:http://groups.google.com/group/envjs
>
> > --John
>
> > On Wed, Feb 25, 2009 at 4:32 PM, d3r1v3d (Gavin Mulligan)
>
> >  wrote:
>
> > > I checked out the jQuery trunk this afternoon and attempted to build
> > > and run the test suite. After navigating to 'trunk/jquery', I ran
> > > 'ant' (for the default build to 'dist/jquery.js') and then 'ant
> > > runtest'. At which point, I encountered a ream of syntax errors. I
> > > noticed that in the built jquery.js file, on line 114, the jquery
> > > version member is set to a string which wraps to the next line before
> > > it terminates.
>
> > > From my build:
> > > 113: // The current version of jQuery being used
> > > 114: jquery: "1.3.3pre
> > > 115: ",
>
> > > This results in the runtest Ant task completely busting from the seams
> > > and, of course, the Yahoo minimizer and other min utilities refuse to
> > > operate upon it. This is curious, since the file which is used to
> > > populate this field (version.txt) does not have a trailing newline,
> > > like I initially suspected.
>
> > > Is this a known issue? I happen to be running an up-to-date version of
> > > Red Hat Linux coupled with Ant 1.7.0. Additionally, I've encountered
> > > the same issue when checking out jQuery 1.3.2 using svn tags.
>
> > > - Gavin
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: Cannot run test framework with fresh SVN checkout

2009-02-25 Thread d3r1v3d (Gavin Mulligan)

Alright, I'll just make do with Make then. Although, I'm curious if
anyone else on the list running Linux and using Ant has run into the
same problem.

Thanks.

- Gavin

On Feb 25, 4:37 pm, John Resig  wrote:
> Umm... I'm not seeing this problem, but then again I'm using the Makefile.
>
> Also, runtest is pretty outdated at his point. That project is being
> maintained over here now:http://groups.google.com/group/envjs
>
> --John
>
> On Wed, Feb 25, 2009 at 4:32 PM, d3r1v3d (Gavin Mulligan)
>
>  wrote:
>
> > I checked out the jQuery trunk this afternoon and attempted to build
> > and run the test suite. After navigating to 'trunk/jquery', I ran
> > 'ant' (for the default build to 'dist/jquery.js') and then 'ant
> > runtest'. At which point, I encountered a ream of syntax errors. I
> > noticed that in the built jquery.js file, on line 114, the jquery
> > version member is set to a string which wraps to the next line before
> > it terminates.
>
> > From my build:
> > 113: // The current version of jQuery being used
> > 114: jquery: "1.3.3pre
> > 115: ",
>
> > This results in the runtest Ant task completely busting from the seams
> > and, of course, the Yahoo minimizer and other min utilities refuse to
> > operate upon it. This is curious, since the file which is used to
> > populate this field (version.txt) does not have a trailing newline,
> > like I initially suspected.
>
> > Is this a known issue? I happen to be running an up-to-date version of
> > Red Hat Linux coupled with Ant 1.7.0. Additionally, I've encountered
> > the same issue when checking out jQuery 1.3.2 using svn tags.
>
> > - Gavin
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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] Cannot run test framework with fresh SVN checkout

2009-02-25 Thread d3r1v3d (Gavin Mulligan)

I checked out the jQuery trunk this afternoon and attempted to build
and run the test suite. After navigating to 'trunk/jquery', I ran
'ant' (for the default build to 'dist/jquery.js') and then 'ant
runtest'. At which point, I encountered a ream of syntax errors. I
noticed that in the built jquery.js file, on line 114, the jquery
version member is set to a string which wraps to the next line before
it terminates.

>From my build:
113: // The current version of jQuery being used
114: jquery: "1.3.3pre
115: ",

This results in the runtest Ant task completely busting from the seams
and, of course, the Yahoo minimizer and other min utilities refuse to
operate upon it. This is curious, since the file which is used to
populate this field (version.txt) does not have a trailing newline,
like I initially suspected.

Is this a known issue? I happen to be running an up-to-date version of
Red Hat Linux coupled with Ant 1.7.0. Additionally, I've encountered
the same issue when checking out jQuery 1.3.2 using svn tags.

- Gavin
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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: New to the jQuery Development Game

2009-02-24 Thread d3r1v3d (Gavin Mulligan)

Thanks a ton.

PS - Sorry for the duplicate post. I'm still a newb when it comes to
newsgroups as well, it seems.

- Gavin

On Feb 24, 10:35 pm, David Zhou  wrote:
> To help with test cases, here are a couple tools to help with the boilerplate:
>
> http://jquery.nodnod.net/http://jsbin.com/
>
> -- dz
>
> On Tue, Feb 24, 2009 at 10:32 PM, John Resig  wrote:
>
> > The best technique to get started is to go in the bug tracker, find an
> > open ticket and to produce a working (or failing, as the case may be)
> > test case if it doesn't have one already. If it passes or fails, bring
> > it to our attention (here on the mailing list) and we can start to
> > look in to it more.
>
> > This is definitely the best way to get started.
>
> > --John
>
> > On Tue, Feb 24, 2009 at 8:44 PM, d3r1v3d (Gavin Mulligan)
> >  wrote:
>
> >> Hey there everyone,
>
> >> I've been interested in joining an open source project for a little
> >> while now and, given that I work with jQuery on a daily basis at my
> >> job, I was thinking of helping out with development - whether it be
> >> tracking down bugs, routine maintenance, or whatever needs doing. I'm
> >> just curious how you guys do things around these parts. In short, does
> >> anyone have any suggestions about how I can 'get my foot in the door'
> >> and start helping out? Is there a special way to go about getting
> >> assigned tickets from the bug tracker or is it programmer a la carte
> >> (to use a delicious analogy)?
>
> >> I apologize for the spam, I tried searching to see if this kind of
> >> stuff has been thrown around in this group before, but came up empty-
> >> handed.
>
> >> Thanks.
>
> >> - Gavin
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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] New to the jQuery Development Game

2009-02-24 Thread d3r1v3d (Gavin Mulligan)

Hey there everyone,

I've been interested in joining an open source project for a little
while now and, given that I work with jQuery on a daily basis at my
job, I was thinking of helping out with development - whether it be
tracking down bugs, routine maintenance, or whatever needs doing. I'm
just curious how you guys do things around these parts. In short, does
anyone have any suggestions about how I can 'get my foot in the door'
and start helping out? Is there a special way to go about getting
assigned tickets from the bug tracker or is it programmer a la carte
(to use a delicious analogy)?

I apologize for the spam, I tried searching to see if this kind of
stuff has been thrown around in this group before, but came up empty-
handed.

Thanks.

- Gavin

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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] New to jQuery Development

2009-02-24 Thread d3r1v3d (Gavin Mulligan)

I'm new to jQuery development and I'd like to pitch in, if possible.
Is there a special way to go about helping to fix bugs in the tracker
(i.e. are they assigned by someone)?

Sorry if this is considered spam, just trying to get my jQuery sea
legs. :)

Regards,
Gavin

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-dev@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
-~--~~~~--~~--~--~---