Re: [jQuery] jQuery Powered Sites - Keep the Links Coming
On 31.03.2007, at 03:15, Rey Bango wrote: Thanks for the submissions!! We're at 151 sites listed to date! w00t! Rey... It seems my earlier submission got lost/forgotten so here it's again: http://www.spin.de/ uses jQuery 1.1.2 since about two weeks. It's a large German language online community (actually one of the largest in Germany). Almost everything dynamic on the site is done with jQuery. We have, in addition to the usual stuff like lightboxes, enhanced forms and AJAX updates, a tabbed chat interface with an AJAX/ Comet based chat completely based on jQuery (in fact, we would not even have dared starting that project without the existence of jQuery - before, JavaScript was just too cumbersome for our taste). Should work with IE 6+, Firefox 1.5+, Opera 9 and Safari -- Markus Peter - [EMAIL PROTECTED] http://www.spin-ag.de/ SPiN AG, Bischof-von-Henle-Str. 2b, 93051 Regensburg, HRB 6295 Regensburg Aufsichtsratsvors.: Dr. Christian Kirnberger Vorstände: Fabian Rott, Paul Schmid ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Known memory leaks?
On 28.03.2007, at 21:01, Brandon Aaron wrote: I think the most likely candidate for the leaks is going to surround the usage of AJAX and Events. Are you attaching events to html pulled in via AJAX? I ask because I believe if you proceed to replace that html without unbinding the events first, that might cause a leak ... but I'm unsure ... just all I can think of for now. Thanks for the tip - we'll be rechecking this. Only the reloading frames are binding events to AJAX-loaded HTML actually, but we'll recheck this. Unfortunately it's not possible to find out which frame is the leaking one - all the tools for leak checks which I've found so far seem to be almost unusable/useless. We've now also patched our copy of jQuery so that the originally IE- only unload handler for unbinding events is executing in all browsers for those parts of our page which reload - just for safety - and now we'll have to wait whether this helps. Astonishingly, we had the least problems with IE though it's not the primary browser for development for us, and this might have something to do with it. -- Markus Peter - [EMAIL PROTECTED] http://www.spin-ag.de/ SPiN AG, Bischof-von-Henle-Str. 2b, 93051 Regensburg, HRB 6295 Regensburg Aufsichtsratsvors.: Dr. Christian Kirnberger Vorstände: Fabian Rott, Paul Schmid ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
[jQuery] Known memory leaks?
Hello We're currently using jQuery 1.1.2 on a production site and have some issues with memory leaks, which seem to affect all browsers after a while, especially Safari, but also Firefox and IE seem to be affected. Users use our page for hours, and parts of the HTML page stay open all the time and are not reloaded for the whole session, which means even small leaks can easily accumulate and become a real problem. We are currently trying to eliminate the memory leaks but are now running into a dead end. The software is unfortunately too large (about 2500 lines of JavaScript code) to easily create reduced test cases for the leaks so we basically have no clue at all, where the leaks occur and whether they are in our code or in jQuery. We noticed the situation improved a bit by upgrading from 1.1.1 to 1.1.2, though. Now, the question is: Are there maybe any already _known_ memory leaks in version 1.1.2 which are maybe even be in the upcoming 1.1.3 or the SVN repository, so we could simply cherry pick the corresponding patches. I tried searching through the ticket database but could not find anything related to memory leaks but might have overlooked someting. So, if any of the developers know of such a bug, it will save us a lot of time. We mainly use the jQuery CSS selection system, event system, animations and AJAX by the way - no XPath -- Markus Peter - [EMAIL PROTECTED] http://www.spin-ag.de/ SPiN AG, Bischof-von-Henle-Str. 2b, 93051 Regensburg, HRB 6295 Regensburg Aufsichtsratsvors.: Dr. Christian Kirnberger Vorstände: Fabian Rott, Paul Schmid ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Known memory leaks?
On 28.03.2007, at 18:32, Dan G. Switzer, II wrote: Markup, What plug-ins are you using on the page? -Dan Hello Dan We use customized versions of the highlightfade, flash and splitter plugins - all of them are inactive most of the time though - the leaks happen if they are not even called, too. The error(s) is either in our code, in jQuery or in the webbrowsers' LiveConnect facilities. We strongly tend to the opinion that it's our fault but I just wanted to ask in case there's some known bug anyway. -- Markus Peter - [EMAIL PROTECTED] http://www.spin-ag.de/ SPiN AG, Bischof-von-Henle-Str. 2b, 93051 Regensburg, HRB 6295 Regensburg Aufsichtsratsvors.: Dr. Christian Kirnberger Vorstände: Fabian Rott, Paul Schmid ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
Re: [jQuery] Detect browser close event
On 19.01.2007, at 12:29, Klaus Hartl wrote: Unai Martinez schrieb: How can i detect browser close event? I've tried something like: I don't think that you can - or if my knowledge here is limited that it is a good idea to - stop the user from closing the window... He could have a try at the proprietary (originally MS-only, but now Gecko also implements it) onbeforeunload Event. That event allows to return a string which is shown to the user who can then choose to either abort the page switch/window close or continue. Due to it's unusual behavior (you have to return the text for Mozilla and set it as returnValue property on the window.event object for IE) there might be problems getting this to work with the jQuery event system, though - I haven't tried this yet. Anyway, that event _can_ be useful if you do not rely on it. It's for example rather helpful for warning users if they entered data into a form without saving (though, of course, AJAX auto-submits give the developer a better amount of control for such issues) -- Markus Peter - SPiN AG http://www.spin-ag.de/ [EMAIL PROTECTED] ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
[jQuery] Small jQuery 1.0.4 problems
Hello
I today upgraded the internal development version of our site from
jQuery 1.0.3 to jQuery 1.0.4. The upgrade caused some minor troubles
which I'd like to report:
We use following simple snippet to get a certain :hover effect for
our tables:
$(table.ruler tbody tr,table.ruler tr).hover(
function(e) { $(this).addClass(ruled); return true; },
function(e) { $(this).removeClass(ruled); return true; }
);
This continues to function but spams the Safari JavaScript error
console with following error message if the mouse pointer hovers
above a text link within the table.
Type error
jquery.js Line: 1036
(line number in reference to jQuery 1.0.4 in the uncompressed
version). This maybe is some problem with the event-object fixer for
Safari.
The effect continues to work, by the way.
Another think I noticed: It seems support for having a string as
second argument to bind vanished since 1.0.3 - it now seems to always
expect a function. This should maybe be added to the changelogs - it
might save others some time in locating problems caused by this
change or the function should complain during the bind about the
incompatible datatype. Right now, jQuery 1.0.4 will happily bind an
event which it cannot handle later on and will die in the
jQuery.event.handle function.
--
Markus Peter - SPiN AG
[EMAIL PROTECTED]
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
[jQuery] unload and unload
Hello I'm a bit puzzled by the existence of two unload functions in jQuery - one which is the unbinder for load, and one which is the binder for unload. Now, the way it's currently implemented, the unload event binder will probably simply overwrite the load unbinder, if I understand the source correctly? I'm a bit concerned about what the behavior is which the API actually guarantees and which I can rely on? -- Markus Peter - SPiN AG [EMAIL PROTECTED] ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
[jQuery] Recommended version
Hello I haven't followed the mailing list for quite some time, so I'm not fully up-to-date: What's the currently recommended jQuery version to use if I'm still in development of my site, do not expect to re-launch it within next 3 months, but want an as-soft-as-possible migration to the next stable version as possible as soon as it's released? I'm willing to live with some bugs in the code while I still develop but I'd like to develop for an as stable API as possible, so I'm a bit reluctant to use the old stable version of jQuery. -- Markus Peter - SPiN AG [EMAIL PROTECTED] Get Firefox! Smaller, Safer, Faster: http://www.spin.de/ffox ___ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
