@samer
Thanks
@anyone
Let me know if you have any questions.
On Jun 24, 9:54 pm, Samer wrote:
> @tres
> Nice plugin
>
> On Jun 23, 7:34 pm, tres wrote:
>
>
>
> > Check this
> > thread:http://groups.google.com/group/jquery-dev/browse_thread/thread/664cb8...
>
> > I've written a plugin to a
I dynamically load jquery into my page and the change that happened at/
round Ticket 2614 (http://dev.jquery.com/ticket/2614) / rev 5970 (or,
in other words, between 1.2.6 and 1.3.2) had, at least for me, a
pretty adverse effect.
Looks like now if jquery is ever loaded after the doc readystate is
Thanks very much for the quick reply John.
I have reconstructed what happened from the various logs and the
emails sent.
(The logging is fairly detailed so the reconstruction is, I feel,
good. There were no browser side exceptions reported at the points I
monitor, which is at failure of AJAX re
Mike -
I'm unfamiliar with this particular situation - if you're able to,
somehow, duplicate it for us that would be very helpful.
--John
On Tue, Jun 30, 2009 at 7:40 PM, Mike Gale wrote:
>
> I have a web site that uses jQuery to populate and manipulate drop
> down lists (option lists).
>
> T
I have a web site that uses jQuery to populate and manipulate drop
down lists (option lists).
They are populated by constructing the options and inserting them
using ...html(...).
The resulting markup and code passes my tests. (I use CSE and other
things to check.)
The site runs this process o
It happened using ie also and monitoring in task manager/perfmon
On Jun 30, 5:41 pm, mharen wrote:
> I'm not sure drip is a good tool for this job. This page:
>
> http://jsbin.com/eyuri
>
> Shows a leak, too, even though I don't even have a ready() event. All
> it does is include jq/jq-ui.
>
> h
I'm not sure drip is a good tool for this job. This page:
http://jsbin.com/eyuri
Shows a leak, too, even though I don't even have a ready() event. All
it does is include jq/jq-ui.
http://www.picvault.info/images/537090310_eyuri.png
Reloading it in IE6 does *not* show a leak in *this* case. The
I'm glad that you're able to reproduce some of the behavior (edited or
otherwise)--I'm not going crazy!
I've read that removing elements makes the problem worse and that
setting the .html to "" is better. I think .empty() does that. I
wonder what happens if you try it with .empty()?
On Jun 30, 1
I would if there was an available vhd of xp with sp1, cant find one on
the ms site.
On Jun 30, 3:53 pm, mharen wrote:
> You're using sp3--which seems to be fixed. Can anyone verify this
> problem with IE6-sans-sp or perhaps with sp1?
>
> Here's drip on my machine, using a now-public pagehttp://
I have maybe spotted another issue but more jquery related.
Whilst playing with your demo page i tried the following, basically
only adding the remove to the datepicker before reloading.
function CheckForRefresh(){
if($('#AutoRefresh').attr('checked')){
You're using sp3--which seems to be fixed. Can anyone verify this
problem with IE6-sans-sp or perhaps with sp1?
Here's drip on my machine, using a now-public page http://jsbin.com/omoya
http://www.picvault.info/images/537090308_omoya.png
On Jun 30, 10:12 am, "jquery.redsqu...@googlemail.com"
w
Sorry should have included that info also, see here
http://gyazo.com/e4ec10e5ae13df428349c1b8f567214d.png.
Cheers
On Jun 30, 2:54 pm, mharen wrote:
> What version of IE6 are you using? I've heard reports that this has
> been fixed in IEsp2 and possibly IEsp1. This is repeatable for me in
> IE-
What version of IE6 are you using? I've heard reports that this has
been fixed in IEsp2 and possibly IEsp1. This is repeatable for me in
IE-sans-sp and IEsp1.
http://stackoverflow.com/questions/1051090/how-can-i-control-ie6jqueryjquery-ui-memory-leaks
Thanks,
Michael Haren
On Jun 30, 8:01 am,
>> live('click') works for most browsers but not IE.
> Try the "change" event, it's more reliable:
> $('select').bind('change', function(){
That will work but not with .live() since the change event isn't
supported with it. The underlying reason, though, is that IE doesn't
bubble change events o
A patch that implements something like this would be considered seriously.
--John
On Tue, Jun 30, 2009 at 6:05 AM, Ricardo wrote:
>
> onerror seems to only work in Firefox. I can only see this implement
> for JSONP with a timeout that removes/empties the callback, it's
> currently impossible f
I am not able to reproduce this, see the following drip leak
screengrab. http://gyazo.com/579a64dc877016ae6d079228fc863728.png
Although memory increases quickly to begin with the gc seems to kick
in at regular intervals leaving a relatively stable footprint. That
seems fine to me considering the
onerror seems to only work in Firefox. I can only see this implement
for JSONP with a timeout that removes/empties the callback, it's
currently impossible for getScript.
On Jun 30, 3:24 am, Paul Bakaus wrote:
> Hi guys,
> working with getScript can be major pain because there's no way to actuall
17 matches
Mail list logo
