Re: [jquery-dev] aborting Ajax calls the success callback

I implemented it exactly as Daniel described in the rewrite and I do believe it's the most logical thing to do. 2010/1/17 Daniel Friesen > Isn't that a loose use of the term "success" originating in confusion > caused by abstraction? > > We call it "success" because that's it's a word describing

Re: [jquery-dev] Re: Ajax error callback in 1.4

FYI, in the ajax rewrite, you get a generic "parsererror". 2010/1/16 Mike Alsup > > Good catch. Filed and fixed:http://dev.jquery.com/ticket/5838 > > Also note that the call to jQuery.handleError in the > onreadystatechange function does not get passed exception string that > may have been throw

[jquery-dev] Ajax rewriting is feature complete...

... including xhr emulation for when people want to re-use the xhr after an ajax call. http://github.com/jaubourg/jquery <= in sync with latest jQuery 1.4.1pre All unit tests (that is jQuery's 1.4.1pre tests + those added for the new features) passing under IE8, FF3.5, Chrome 3.0, Safari 4.0 and

Re: [jquery-dev] Re: jQueryLINT

I so agree with you here, Dave. Design by contract is all I have to say. 2010/1/15 Dave Methvin > > "Not technically demanding" uh? > > I beg to differ on this one. > > Conceptually it's a simple idea: Inspect the parameters being passed > to jQuery and its methods, then see if they match the A

Re: [jquery-dev] Re: jQuery.support.nonstandard_json_string

As commented in your commit, I think the support approach is cleaner and more future-proof (that is when Chrome implements JSON parsing controls properly). 2010/1/12 John Resig > As a note: I added identical errors earlier today but skirted around > the need to have any sort of support property:

Re: [jquery-dev] Remove JSON.parse from 1.4

That's all nice & dandy for json. But the "javascript getting executed solely on server saying so" problem still remains. The fact you had to change the synchronous request tests is a clear proof of the problem to me: existing code will break (no issue if documented), existing code will face a secu

Re: [jquery-dev] Remove JSON.parse from 1.4

What I'm worried about is attacks on existing pages. So far, in jQuery, executing javascript was borded to conscious actions by devs: - inserting HTML in the document (ajax doesn't execute embedded script automagically), - jsonp, - specific ajax wrappers (getScript, load) or cross-domain access to

Re: [jquery-dev] Remove JSON.parse from 1.4

I'll quote what I said in the $.ajax "auto" discussion (see last 2 paragraphs especially): > > There's something significant behind the buzz, though. I really don't > want > > to read the announcement: "ATTN everyone using jQuery.ajax(). If you're > > going to update your library or if you're link

Re: [jquery-dev] Re: Performance issues using $.ajax async

If only it could be enough to set onreadystatechange to null :( Anyway, just a note to let you all know the polling is syndicated between all requests in the ajax rewriting (ie: only one timer no matter how many requests are being made concurrently). 2009/12/30 jblebrun > On Nov 13, 3:12 pm, Jo

Re: [jquery-dev] GOALS? Feature Request: $.ajax(): Detect json via response header

> > There's something significant behind the buzz, though. I really don't want > to read the announcement: "ATTN everyone using jQuery.ajax(). If you're > going to update your library or if you're linking to the latest on google > and it's updated FOR you without your knowledge, you MUST first go t

Re: [jquery-dev] GOALS? Feature Request: $.ajax(): Detect json via response header

So it was pure #2 obviously, not #1. 2009/12/29 Julian Aubourg > Again, why not do this with an Accept header? >> >> Client sends acceptable content types, server responds with a content >> type, if the server's response is one of the accepted types, jQuery >&g

Re: [jquery-dev] GOALS? Feature Request: $.ajax(): Detect json via response header

;>> >> wrote: >>> >> > Seems like a lot of awkward wheel reinventing going on here. Content >>> >> > type negotiation is a feature of HTTP; is there a reason we aren't >>> >> > using it? >>> >> > >>> &g

Re: [jquery-dev] Re: Feature Request: $.ajax(): Detect json via respons e header

n fact, greatly > desire such a new setting. I'll know that my live apps that are using > dataType: null will be unaffected and in the future I'd be able to > write ajax calls that can respond to various data types. Also, I've > suggested several approaches and look forward to

Re: [jquery-dev] Re: Feature Request: $.ajax(): Detect json via respons e header

tyle. Regardless, I'm > leaning towards the dataType: "auto" approach as it's easy to use/ > implement and affords enough control. > > > Julian Aubourg wrote: > > > As for string expressions not being in the calling style of jQuery... > > well... I rea

Re: [jquery-dev] Re: Feature Request: $.ajax(): Detect json via res pons e header

> Rick > > -- Sent from my Palm Prē > > ------ > Julian Aubourg wrote: > > First of all, merry christmas ;) > > This affords the most control but may be difficult to implement >> elegantly as the obvious choice of an array has already be

Re: [jquery-dev] Re: Feature Request: $.ajax(): Detect json via respons e header

cause some confusion for developers when they're initially > learning the difference between "auto" and dataType's default behavior > (xml/html). Obviously, people using this setting should ensure they > are calling trusted, competent servers. > > > 7) dataType

Re: [jquery-dev] Re: Feature Request: $.ajax(): Detect json via res pons e header

on the most recent version of > ajax.js in the master on github. > > The 'how'... Its shockingly simple: it copies the same behaviour as the xml > detection. Nothing special. > > Rick > > -- Sent from my Palm Prē > > -- > Julian Au

Re: [jquery-dev] Re: Feature Request: $.ajax(): Detect json via respons e header

I'm a bit curious as to how (and why) you intend to implement this, seeing as the ajax revamping I've been working on uses an array of dataTypes. For example s.datTypes = ["jsonp","xml"] means: get an object (a string in that case) over jsonp that'll get parsed as xml (and this is actually working

Re: [jquery-dev] Feature Request: $.ajax(): Detect json via response header

With the upcoming new ajax code, it should be doable. 2009/12/22 webbiedave > Hello. > > Could we change the $.ajax() function to treat the server's response > as json if dataType is unspecified and the response content-type is > "application/json"? > > Thanks, > Dave > > -- > > You received thi

[jquery-dev] IRC

I know, it'll sound silly but I've been hanging in the jquery-dev chan for some time now and nobody talks :P Or am I being modded by Chanserv? -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...

Re: [jquery-dev] jQuery require and script loaders

OK, so I finally got time to write some docs & unit tests for my own baby... and here comes Dominoes: http://code.google.com/p/javascript-dominoes/ See the Wiki pages to get an idea of what it is capable of (quite the wall of text there but heh). It is more of a general purpose "scheduler" and pr

Re: [jquery-dev] Can't build files after latest commit

No issue building on Vista with latest JDK, fyi. 2009/12/19 Karl Swedberg > I found this thread on Closure Compiler Google Group: > > > https://groups.google.com/group/closure-compiler-discuss/browse_thread/thread/79514964f16ec591/42d0f9210a552e74?lnk=gst&q=bad+version > #42d0f9210a552e74 > ( ht

Re: [jquery-dev] About the group

We'll > have plenty more details when we get closer to the final switch. > > --John > > > > On Thu, Dec 17, 2009 at 8:33 PM, Julian Aubourg > wrote: > > I was browsing John's blog (because I sometimes like a good read) and I > came > > upo

[jquery-dev] About the group

I was browsing John's blog (because I sometimes like a good read) and I came upon this post I hadn't seen before: http://ejohn.org/blog/google-groups-is-dead/ First of all, thanks to all those that moderate this list and the others (I wasn't aware of the nightmare behind). I was curious, though, a

Re: [jquery-dev] Re: Event module in repository

Any help remote-debugging this issue would be > appreciated. > > --John > > > > On Wed, Dec 9, 2009 at 11:29 AM, Julian Aubourg > wrote: > > OK, I tested to be sure. Latest source tree does not pass tests in IE. > > > > 2009/12/9 DBJDBJ > >> >

Re: [jquery-dev] Re: Ajax refactoring V2

7;s something > that we'd ship in jQuery core. > > Glad to hear that it's really coming together, though! > > --John > > > > On Wed, Dec 9, 2009 at 11:33 AM, Julian Aubourg > wrote: > > Another update: I added a jsonp over iframe transport similar

[jquery-dev] Re: Ajax refactoring V2

$.ajax and $.ajax.createRequest but we're almost there. On 8 déc, 23:56, Julian Aubourg wrote: > Just comitted version 2 of the ajax refactoring for those interested. The > tree is in sync with latest jQuery tree. > > No more global transport selection function: transports

Re: [jquery-dev] Re: Event module in repository

, 4:15 pm, John Resig wrote: > > The code as of when 1.4a1 came out was passing 100% in IE 6, 7, and 8. > > I'm away from an IE-capable computer at the moment (traveling) so I'm > > not sure if it's still the case - at least it was as of last Friday. > > > &g

[jquery-dev] Event module in repository

Just curious, do the event module unit tests pass in IE ? Acts all weird for me (including a nasty redirection) but I'm not sure if it's because of my ajax rewriting or not. -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this g

[jquery-dev] Ajax refactoring V2

Just comitted version 2 of the ajax refactoring for those interested. The tree is in sync with latest jQuery tree. No more global transport selection function: transports are now bound to dataTypes through jQuery.ajax.bindTransport( dataTypeSelector, factoryFunction ). The dataTypeSelector is a st

Re: [jquery-dev] Ant build

My bad, I see what you changed and I didn't merge properly. 2009/12/8 Julian Aubourg > After I added git to my path (I used the bash version), it is still not > working: > > BUILD FAILED > C:\wamp\www\zend\jQueryJulian\jquery\build.xml:44: > C:\wamp\www\zend\jQueryJulia

Re: [jquery-dev] Ant build

After I added git to my path (I used the bash version), it is still not working: BUILD FAILED C:\wamp\www\zend\jQueryJulian\jquery\build.xml:44: C:\wamp\www\zend\jQueryJulian\jquery\${SRC_DIR} not found. Worked flawlessly (with manual git cloning/pulling of qunit & sizzle) before. I'm under Vista

Re: [jquery-dev] Re: What's wrong in my code?

*2* DBJDBJ ! Scary ;) /me hides 2009/12/8 Daniel Friesen > More like Google Groups strikes again. John already noted how bad Google > Groups is in dealing with address spoofing. > > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name] > > DBJDBJ wrote: > > This made me to imm

Re: [jquery-dev] make breaks after pulling commits from GitHub

Still not working, there seems to be a remaining nodeNode in manipulation.js (line 466 -- also in need of an elem.nodeName test too btw). /me nods ;) 2009/12/7 John Resig > Fixed the missing brace: > > http://github.com/jquery/jquery/commit/97323d192f368fb8fa4ab8c77fbd7da99b049800 > > And chang

Re: [jquery-dev] make breaks after pulling commits from GitHub

Commented about it here : http://github.com/jquery/jquery/commit/7d36ccfa8eb018fcf349e1f74e3a0a614385558f 2009/12/7 Karl Swedberg > I pulled in the latest changes this morning from the jQuery GitHub repo, > but when I tried to run "make" it threw a couple errors: > > ERROR] 1:0:Compilation produ

Re: [jquery-dev] Re: problem with use of null in jQuery.speed

Hey John, saw my comment here: http://github.com/jquery/jquery/commit/25b0ba9f9612583033b902a0e40345463a3a71d0? 2009/12/5 John Resig > Just landed the fix: > > http://github.com/jquery/jquery/commit/b776e2b79a5b051fba3091b0b5057ae14950f7cc > > Thanks! > > --John > > > > On Fri, Dec 4, 2009 at 10

Re: [jquery-dev] Re: ajax module: no complete event on abort

Thanks for the links, Dave. #3984 should be fixed in new implementation and I just comitted a patch that takes care of #5280. I also moved code around to handle a problem discussed in dojo: http://trac.dojotoolkit.org/ticket/9486 Still, doesn't answer my initial question though I'm quite happy to

Re: [jquery-dev] jQuery 1.4 Alpha 1 Released

Nice, I'll be sure to test it :) 2009/12/4 Elijah Insua > Awesome! > > Great work guys! > > -- Elijah > > > On Fri, Dec 4, 2009 at 3:44 PM, John Resig wrote: > >> More details here: >> http://blog.jquery.com/2009/12/04/jquery-14-alpha-1-released/ >> >> --John >> >> -- >> >> You received this me

[jquery-dev] ajax module: no complete event on abort

While refactoring $.ajax, I realized aborting a request doesn't fire complete. While this could make sense for early abort (beforeSend) since ajaxStart hasn't been fired yet, it is quite awkward later on when timeout does fire the event while being nothing more than an automated abort. I also noti

Re: [jquery-dev] Re: $.ajax feature matrix

/jaubourg/jquery/blob/7980f80181262ba65dc9de19d254deb0752d7269/src/transports/xhr.js Definitively back-portable into current implementation. 2009/12/3 Julian Aubourg > isPlainObject? > > Anyway, progress again on the transport front. Transport definition reduced > to 2 functions (

Re: [jquery-dev] Re: $.ajax feature matrix

isPlainObject? Anyway, progress again on the transport front. Transport definition reduced to 2 functions (the response headers are now passed to the complete callback which is simpler and more elegant). Also, the new architecture didn't prevent the infamous memory leak when using onreadystatechan

Re: [jquery-dev] Re: $.ajax feature matrix

Nevermind I found the way ;) So, 100% tests passing in IE8, latest safari, latest chrome, latest Opera and latest Firefox. Still searching for a decent solution to the pluggable aspect of transports. 2009/12/3 Julian Aubourg > And here I ask the git newb question? How do I sync my branch w

Re: [jquery-dev] Re: $.ajax feature matrix

And here I ask the git newb question? How do I sync my branch with your latest changes? 2009/12/3 John Resig > > Yep, like I said earlier > > jQuery.isObjectLiteral(document.createElement("div")) returns true in IE8 > > (dunno for earlier versions) but John seems to be working on it. Can't > > b

Re: [jquery-dev] Re: $.ajax feature matrix

> Unfortunately this type of change will break plugins such as > jquery.ui.tabs but judging by other changes you've been discussing, it > seems that there will be many breaking changes. I'm doing my best so that it doesn't break anything, hence my current focus on unit testing right now. -- You

Re: [jquery-dev] Re: $.ajax feature matrix

gt; defaults. For some reason it worked fine when I passed window.document > instead. > > George > > On Dec 2, 4:03 pm, Julian Aubourg wrote: > > I started cleaning the code and I think it's already in a good enough > shape > > now for some code reviews/remarks/ide

Re: [jquery-dev] Re: $.ajax feature matrix

the correct agent given a type and how do you handle priority so that overriding your agents is easy? 2009/12/2 Scott Sauyet > On Tue, Dec 1, 2009 at 8:21 PM, Julian Aubourg > wrote: > > Anyway, the code has been comitted at http://github.com/jaubourg/jquery > > Just started l

Re: [jquery-dev] Re: $.ajax feature matrix

in another one and return that > }); > > > My point is, instead of really re-wiring all the internals of $.ajax, > couldn't we just use this plugin to substitute in a "smarter" XHR > object that all the different features we want? > > --Kyle > > > >

Re: [jquery-dev] Re: $.ajax feature matrix

I confirm that jQuery.isObjectLiteral(document.createElement("div")) returns true under IE8. 2009/12/2 Julian Aubourg > I started cleaning the code and I think it's already in a good enough shape > now for some code reviews/remarks/ideas, etc. > All tests pass unde

Re: [jquery-dev] Re: $.ajax feature matrix

docs.jquery.com/JQuery_Core_Style_Guidelines > > Naturally, making sure that all the tests pass as well is a great way > to make sure that the code lands. > > --John > > > > On Tue, Dec 1, 2009 at 8:21 PM, Julian Aubourg > wrote: > > Thanks Dave but I think I

Re: [jquery-dev] Re: $.ajax feature matrix

Thanks Dave but I think I kinda figured it out! Anyway, the code has been comitted at http://github.com/jaubourg/jquery I don't have time to write everything about it down right now but you can all have a look at least. 2009/12/2 Dave Methvin > > OK, so I have implemented my solution: > > > An

Re: [jquery-dev] Re: $.ajax feature matrix

er Windows "Evil" Vista but I had no problem using ant, updating the ant build file and the makefile. Go figure. So, if anyone has clear step in order to commit with this zealot, please do share before I commit suicide. I made a fork of jQuery on github btw. -- Julian 2009/11/19 Julian

Re: [jquery-dev] HOTTEST SXXY BRAZILIAN BUBBLE BUTT SAMBA DANCER IN THE WORLD

.remove() ? 2009/11/24 Samer Ziadeh > $.hell('YES!'); > > > On Mon, Nov 23, 2009 at 21:22, wrote: > >> Beautiful Brazilian Girls xe2x80x93 Samba mixed with Hip >> Hop >> Baile >> Funk Brazil

Re: [jquery-dev] Re: $.ajax feature matrix

this gets bumped until after 1.4 - it > sounds like a lot of code might be changing and I'd rather do it right, > once, then badly twice. > > --John > > > > On Wed, Nov 18, 2009 at 10:52 PM, Julian Aubourg > wrote: > >> Not yet, I'll wait to have at leas

Re: [jquery-dev] Re: $.ajax feature matrix

this sounds pretty good - do you have a link to the code? > (Preferably in a fork up on Github - makes it easy to do a code review.) > > --John > > > > On Wed, Nov 18, 2009 at 10:10 PM, Julian Aubourg > wrote: > >> OK, just a post to keep you all updated since I di

Re: [jquery-dev] Re: $.ajax feature matrix

puted option, it should be very easy to handle all situations (by throwing an exception or whatnot so that client code could fallback on a proxy or something). Feedbacks welcome is you see anything gross in there. -- Julian 2009/11/15 Julian Aubourg > I looked into your code and we basic

Re: [jquery-dev] Re: $.ajax feature matrix

lesome is in the properties > > > >> that xhr provides (like readyState, responseXML, etc.). I'm not sure > > > >> how you'd build this mock XHR and keep those properties up to date. > > > > > On Thu, Nov 12, 2009 at 10:14 PM, Julian Aubourg &

Re: [jquery-dev] Re: $.ajax feature matrix

Well, the idea is to enable Jason Persampieri's idea of a chaining ajax system (ie $.ajax(options).success(...).error(...) ) while not having race conditions (so the bind method will be smarter than your usual one) and while maintaining compatibility with xhr. So basically, all ajax request system

Re: [jquery-dev] $.ajax feature matrix

Oh yes, also, ajax could handle image preloading too imo. 2009/11/12 Julian Aubourg > Regarding the abort possibility for jsonp (#5500 => #3442), this brings us > back to the idea of returning an abstraction on top of the actual xhr/script > hack/whatever. > > I was curious a

Re: [jquery-dev] $.ajax feature matrix

Regarding the abort possibility for jsonp (#5500 => #3442), this brings us back to the idea of returning an abstraction on top of the actual xhr/script hack/whatever. I was curious as to why the whole ajax typology wasn't implemented with a factory pattern: you would call something like XHRFactory

Re: [jquery-dev] $.ajax feature matrix

Very nice and it will definitely help newcomers. A note though about "cache" in "jsonp" mode: if you use the automatic fetching of a callback name on the secondary question mark, the name being generated, browsers will never ever cache (how could they? The content is actually different)... and sin

Re: [jquery-dev] Re: Calling callback in $.post & $.get on error

Just regarding the issue of jsonp, I'll ponit you to my own jsonp plugin: http://code.google.com/p/jquery-jsonp/ I too agree jsonp is a bit too specific for an inclusion within $.ajax but the proposed solution of returning a wrapper around the xhr could help smoothing out differences. Regarding th

Re: [jquery-dev] Re: Calling callback in $.post & $.get on error

Yeah, $.ajax already returning jQuery(xhr) would be awesome, but talk about backward compatibility breakage... the real question being: how many actually do use the xhr as a returned value (as opposed to beforeSend for instance). I have a question though... would jQuery(jQuery.get("url")).bind("su

Re: [jquery-dev] Re: Calling callback in $.post & $.get on error

s compatibility)... that could lead to > > $.get(url).success( callback ).error( callback ). > > Interestingly, this would lead to the ability to cleanly request a > resource, then define how you want to handle it later on, even after > it's already come back. > > That&

Re: [jquery-dev] Calling callback in $.post & $.get on error

ent: "Really the get and post > methods are meant to be simple cases, everything else should be > tackled with the ajax method." > > --John > > > > On Mon, Nov 9, 2009 at 4:48 PM, Julian Aubourg > wrote: > > Well, to be honest, I never ever use $.get or $.

Re: [jquery-dev] Calling callback in $.post & $.get on error

Well, to be honest, I never ever use $.get or $.put (or $.getJSON). The main reason is that there is no error callback which, in my opinion, makes them completely useless in any production environment. Now I understand the convention being broken argument, but the two callback solution: - does not

Re: [jquery-dev] Calling callback in $.post & $.get on error

Wouldn't it still break some scripts that actually expect the data never to be undefined? Why not the following: $.get("someurl", function(data) { // got results }, function(errorMessage) { // got error }); That way, actual scripts behave as usual and new ones can provide an error callba

Re: [jquery-dev] Calling callback in $.post & $.get on error

As simple as they should be I always wondered why $.get (and $.getJSON) and $.post don't have the option to provide an error callback as a third parameter. I mean, simple cases don't protect from temporary connection and/or server shutdowns, do they? With the current success callback only design, i

Re: [jquery-dev] Making backgroud inactive and blur when a popup panel loads

You just use a div that covers the whole body below the popup div and, thus, intercepts clicks. You can toy with the div background color and opacity to get a "page fading out" effect. You can also have that "cache" div handle click to close the popup. Anyway, this question would better suited for

Re: [jquery-dev] Re: 'hover' pseudo element - access thru jQuery?

it could be implemented by finding the rule using > document.styleSheets? Or is there some technical hurdle that would > make this impossible? > > Best regards, > Jeremy Morton (Jez) > > On Nov 1, 1:55 pm, Julian Aub

Re: [jquery-dev] 'hover' pseudo element - access thru jQuery?

You could protect your rules with a noscript tag: .show { color: red } Hello world In this example, the span would only be in red when javascript is off. 2009/10/31 jez > Hi all, > > I have a minor pr

[jquery-dev] Re: Ajax post request times out on Safari

I'm guessing webkit somehow postpones the actual ajax call. Have you tried with Chrome? Anyway, I'm puzzled by the use of timeout. If you don't expect any answer from the server, simply do not provide any success callback. Using a timeout could have the consequence of cancelling the operation serv

[jquery-dev] Re: Get a selector path from a jquery object

The issue with simple code like this are siblings. 2009/7/30 DBJDBJ > > Or , maybe : > > function xpath ( selector ) > { > var retval_ = [], xpath_ = "" ; > $(selector).each( function (){ > var e = this ; > do { > xpath_ = "/" + e.tagName + (e.id ? "[...@id=" + e.id +"]" : "")

[jquery-dev] Re: #4833 isXml function throws an error in IE when used in combination with an iframe

Andrea, John, you made my day :) Now I have to clean up my keyboard. Note to self, never ever read the jQuery-dev mailing list with Diet Coke in your mouth. 2009/7/27 Andrea Giammarchi > damn it :D > > > On Mon, Jul 27, 2009 at 2:22 PM, John Resig wrote: > >> Too late: >> http://dev.jquery.com/

[jquery-dev] Re: $.ajax's error callback: Confusion with status codes and dataType

I really, really like what you did here, Nathan. Behavior of $.ajax could be: option[response.code] ? option[response.code](infos) : error(infos) So basically, any response code that is not 200 is considered an error BUT you can specify a specific error callback per type of response. Would that be

[jquery-dev] Re: Using .val() with

Well, you could very well imagine a site with a guy using 666 or 69 or any other l337 name as his username. If you happen to have a select with a list of users (friends list for instance), with option values being the user id, you can end up with Mr. 69 being confused with user which id is 69. A wo

[jquery-dev] Re: Rename bind/unbind?

I've been watching this thread from afar and I don't really get it. This is OO programming and it's quite common to have different classes having methods with the same name but different semantic (obviously since, again, they are different classes). someFunction.bind() has semantic within the Func

[jquery-dev] Re: new $

ow for some of the debugging > features being discussed. > > -- dz > > > > On Tue, May 19, 2009 at 9:00 AM, Julian Aubourg > wrote: > > I dunno. > > From what I witnessed, when jQuery starts to complain/halt, the problem > is > > generally els

[jquery-dev] Re: new $

it's feasible to monkeypatch debugging wrappers around > jQuery core methods. You don't even need it to throw errors -- a > simple console.log warning would suffice. > > -- dz > > > > On Tue, May 19, 2009 at 8:38 AM, Julian Aubourg > wrote: > > jquery.deb

[jquery-dev] Re: new $

jquery.debug.js / jquery.release.js ? ;) I really like this idea. When I first started using jQuery, I sometimes had some issues determining what it was I was doing wrong when jQuery complained deep in its internal functions. 2009/5/19 Matt Kruse > > On May 19, 5:32 am, DBJDBJ wrote: > > This i

[jquery-dev] Re: globalEval in high conflict situations.

window/document dependent methods to work with other windows/documents than > the one jQuery is loaded in. I believe there are still some patches to be > made but overall jQuery 1.3.3 should operate better under situations like > this. > -- > Brandon Aaron > > > On Wed, A

[jquery-dev] Re: globalEval in high conflict situations.

Yep, the someone was me. And as Daniel points out, the problem with sandboxing is that it is permeable but not transparent. You could go around onstart manipulations by hacking the script (i.e. point to window.top rather than window) but you'd also have to hack into all of the script's functionalit

[jquery-dev] Re: Plugin local variables

A usual technique for having variables local to a plugin is to use function scoping like this: (function($) { var firstVar = ...; var secondVar = ...; $.pluginFunction = function() { ... }; })(jQuery); 2009/4/12 Alexandre Marinho > > Hi, i'm tring to reproduce a library of mine fr

[jquery-dev] Re: Centering on the viewport

-> Save Page As" from the browser. > > Which I then vivisect in VisualStudio debugger. > > > > BTW: when you point your IE6/7 tohttp://dbjsystems.com/jq/, the > > jQuery.support.boxModel is false, yes ? jQ can not gurantee consistent > > positioning and dimensioning if boxModel i

[jquery-dev] Re: Centering on the viewport

... and by Brian I meant Brandon :( Yeah, I'm that good with first names, sorry :/ 2009/4/7 Julian Aubourg > I know that, DBJ and that's the whole problem for me : I was strictly > unable to trigger the bug on simpler pages. So, basically, I have to strip > down the current o

[jquery-dev] Re: Centering on the viewport

(and that's counting a memory leak in a C/Prolog application with no proper memory inspection tools back in the days). Never thought I'd miss those days Oo -- Julian 2009/4/7 DBJDBJ > > Julian , you have to present *much* simpler example ... We can not > debug your html + css, sorry.

[jquery-dev] Re: Unit testing with network requests

mulate network traffic. We don't include cross-domain > tests but that's mostly because we'd rather not rely on the quality of > someone else's server/network connection when running the tests. > > --John > > > > On Thu, Apr 2, 2009 at 2:46 PM, Julian Au

[jquery-dev] Re: Centering on the viewport

e, that displays the values of the jQuery.support and add it to > your problem page. I am curious what will be the boxModel result ? > With your doctype and with the one above. > > On Apr 1, 4:30 pm, Julian Aubourg wrote: > > I DID remove the prolog to no avail. > > > > 200

[jquery-dev] Unit testing with network requests

Hi all, I'm turning to you once more for a problem I think you can help me with. So far, for my jsonp plugin (for those who don't know of it: http://code.google.com/p/jquery-jsonp/), I just made a simple test page using the YouTube data API. I have the plugin working in production so I know it's s

[jquery-dev] Re: Centering on the viewport

e of all other browsers will nicely > switch to "standards mode" ... Try. > > > > On Apr 1, 12:54 pm, Julian Aubourg wrote: > > I seriously doubt it given:1) It works in every other browser (PC and MAC > > versions) > > 2) It worked with 1.2.7 > &

[jquery-dev] Re: Centering on the viewport

> found simple json strings that do not work, and there is already IE8.1 > being promissed, so nothing very new in that corner ... > > > > On Apr 1, 2:19 pm, Julian Aubourg wrote: > > I'm strictly unable to trigger any of the bugs even if I copy paste the > > popup

[jquery-dev] Re: Centering on the viewport

gt; On Wed, Apr 1, 2009 at 5:54 AM, Julian Aubourg > wrote: > >> I don't know if something changed with the 1.3.2 version shared on google >> but the viewport size is now correct Oo. >> Anyway, I have a couple more problems (though I found workarounds). They >> a

[jquery-dev] Re: Centering on the viewport

ich is still called "quick test" ... ;o( > > On Apr 1, 12:29 pm, Brandon Aaron wrote: > > Could you show me the markup of the page that you are having these issues > > on? > > -- > > Brandon Aaron > > > > On Wed, Apr 1, 2009 at 5:54 AM, Jul

[jquery-dev] Re: Centering on the viewport

09/3/30 Brandon Aaron > You could pull in the window logic from 1.2.6 ( > http://dev.jquery.com/browser/tags/1.2.6/src/core.js#L1338 ) into the > 1.3.2 release ( > http://dev.jquery.com/browser/tags/1.3.2/src/dimensions.js#L25 ). > -- > Brandon Aaron > > > On Mon, Mar 3

[jquery-dev] Re: Centering on the viewport

the 1.3.3 > release but I'm unsure when that release will happen right now. I should be > able to allocate some time to fix this issue soon though if you don't mind > using a nightly build once it is fixed. > -- > Brandon Aaron > > > On Mon, Mar 30, 2009 at 2:14 PM

[jquery-dev] Centering on the viewport

Hi all, I'm in the process of migrating a site from 1.2.7 to 1.3.2. So far, I just ran into a bug in webkit browsers that forced me to rewrite "expr1, expr2, ... exprN" selectors into loops (I suppose you're aware of this one). I also have trouble with attaching event handlers to dynamically creat

[jquery-dev] Re: adding method to custom namespace

I don't think it is possible. No matter how you turn it around, you'll lose the object context. I suppose your myNamespace() function is something like: $.fn.myNamespace = function() { return this; } right? 2009/3/28 iceman2g > > I asked this elsewhere and it was suggested that I ask here.

[jquery-dev] Re: replaceClass

quot;) + " ").indexOf(" " + className > + " "); > > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) > > Julian Aubourg wrote: > > And gmail borked the sample page link :/ > > http://www.tfuture.org/julian/classname.html > > > >

[jquery-dev] Re: replaceClass

en (Dantman, Nadir-Seen-Fire) > > Julian Aubourg wrote: > > It may seem conter-intuitive but, in the end, the less you handle within > the > > VM the better. Since I want to support regexps, why make some special > code > > with branching and javascript based handling

[jquery-dev] Re: replaceClass

A tiny bit of trickery, and that could be turned into a good possibility. > > (" " + node.className.replace(/\s+/, " ") + " ").indexOf(" " + className > + " "); > > ~Daniel Friesen (Dantman, Nadir-Seen-Fire) > > Julian Aubourg wrote: > >

[jquery-dev] Re: replaceClass

And gmail borked the sample page link :/ http://www.tfuture.org/julian/classname.html 2009/3/27 Julian Aubourg > So, I talked about making a plugin I would be the only one to use, didn't > I? ;) > http://www.tfuture.org/julian/jquery.classname.js > > The test p

  1   2   >