1.7 rc2 is supposed to handle the cleanup for you in most cases. See
http://www.prototypejs.org/2010/5/13/prototype-1-7-rc2 (use
Element.purge)
On May 21, 1:06 am, orbiter wrote:
> I recently discovered Element.store and Element.retrieve and I'm
> wondering a little about the semantics. Mainly I
stener( 'blur', DelegationExplorer.directHandler,
true );
} else {
// IE supports focusin and focusout
myRoot.observe( 'focusin', DelegationExplorer.directHandler );
myRoot.observe( 'focusout', DelegationExplorer.directHandler );
}
where frm is again an ances
Thanks,
I went over to lighthouse and found:
https://prototype.lighthouseapp.com/projects/8886/tickets/666-make-focus-blur-bubbles
so it is 'scheduled' for 2.0
If I need it (beyond my exploration code), I'll just have to roll my
own for now :(
--
Phil
--
You received this message because you a
Environment: Prototype 1.7 rc2; XAMPP on Ubutnu 10.4 (running as
VirtualBox vm); browsers: FF3.6.3 (localhost on Ubuntu 10.4); FF3.6.3
(Win XP SP3 over lan); IE8.0.6001 (Win XP SP3 over lan)
Using Element.on [$(ele).on( 'click', '.special', callback);] triggers
a callback for clicks inside of ele
I wrote my own code from a completely different direction before I saw
this. That code adds new events to the standard code that do bubble.
It looks cleaner than what I did. I added a 'wrapper' around the
standard code, with extra handling for the problem cases. I also
added a descendant check t
I don't think you understood my question. I understand that event
delegation means that events bubble up from the element the event
actually occurred on, to the ancestor element that the event
[listener] was attached to. And that the events that reach that
listener / handler are filtered based on
Multiple counters are not *necessary* for this, assuming you mean
count down timers to the end of the bidding for each item. Just need
to display (formatted) the difference between 'now' and the bid end
time (watching for timezone differences).
If you mean counters for different numbers of bids f
TJ, that explains the symptoms I was getting when writing a piece of
*Reflection* code to explore the DOM and javascript library code. I
made it work, but did not understand WHY I needed to massage some
things to get reasonable results.
Got to keep learning :)
--
Phil
--
You received this messa
greg,
Nothing to do with Prototype. Standard javascript / DOM
> If I do:
> for (m in c) console.log(m)
> I get a nice list of all variables and methods, but typeof m always
> returns 'string'.
for (a in b)
always sets 'a' to be a string. It is the 'name' of the property in
'b'.
Try console.l
