On 8/17/07, kangax [EMAIL PROTECTED] wrote:
Writing to attributes is fine but for custom properties I ended up
with this little helper (I know the name is idiotic but I had no time
to think of a good one):
Element.addMethods({
__extend: function(element, hash) {
return
Hi Guys,
first of all I want to thank all of you for producing such a great
framework and so many great new futures for 1.6.0.
I couldn't wait to try them out and replaced my prototype 1.5.1 lib with
the new 1.6.0rc0. I had to switch some things because I some of my
constructs were
Hello,
Before 1.6, I had a set of functions on top of the Event.observe
family of functions, which dealt with registering callbacks for
events, like this:
signalConnect: function(element, name, observer) {
if (!element || !name || !observer) return;
if (!element.signals)
On 8/17/07, Viktor Kojouharov [EMAIL PROTECTED] wrote:
However, there's still the issue of having
support for global element events, like 'mousewheel', 'mouseenter',
and 'mouseout', that would work with all elements, and reuse existing
event names to achieve their function.
In the old
On Aug 17, 1:24 pm, Mislav Marohnić [EMAIL PROTECTED]
wrote:
On 8/17/07, Viktor Kojouharov [EMAIL PROTECTED] wrote:
However, there's still the issue of having
support for global element events, like 'mousewheel', 'mouseenter',
and 'mouseout', that would work with all elements, and
Both would be excellent uses for it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send
Also is there any validity in the concern that without proper checks
the window.onload trigger could happen in the middle of executing the
contentloaded observers (esp. in IE when you are emulating a
contentloaded event)?
Do you have a way to ensure proper first in first out order or event
This is probably the most glaring flaw in RC0: any event types that
are not part of the DOM L2 Events spec, but are nonetheless honored by
one or more browsers, are handled incorrectly by Prototype as custom
events.
We've got to figure out a way around this, even if it means we create
a
What is the feeling on adding functions to Date.prototype? As mentioned
in March (see message at bottom), adding Date.prototype.succ() would
allow some helpful iterating. I would suggest an optional argument to
succ for time period and I also would like to throw out several more
possible
Prototype.Browser.IE and the others are booleans, not functions that
return booleans.
Cheers,
Matt
On Aug 7, 3:06 am, Lino Jan Telera [EMAIL PROTECTED] wrote:
For browser u can write (only if you are using prototype 1.5.1)
Prototype.Browser.IE (return true if you are using IE)
10 matches
Mail list logo
