Are there any plans for prototype to implement and standardize the
onHashChange call back?
https://developer.mozilla.org/en/DOM/window.onhashchange
IE8, Firefox 3.6 supports it
I think this would be a good tool to have and since browsers are slowly
implementing it--we can check for it existence.
I came across this problem myself. I think prototype should provide some
type of API for things like this. In all my apps, I have a prototype_ext.js
file that make small modifications/enhancements to prototype. It would be
nice to be able to do something like this:
prototype_ext.js:
Would it be reasonable to implement it so that Element.insert takes as many
content as you pass it? This will exclude insertion points of course...
container.insert(part1);
container.insert(part2);
container.insert(part3);
would be:
container.insert(part1, part2, part3);
Thanks.
It would be nice if Event#observe's eventName argument was able to take an
array, or perhaps a comma delimited string so that it can attach to multiple
events in one call:
Event.observe(something, 'keyup,mouseup', this.blah.bind(this));
or
Event.observe(something, ['keyup', 'mouseup'],
Sorry for getting off topic, but I completely agree with Jim. I'm currently
writing a complicated WYSIWYG editor and one of the annoyances I'm faced
with is the fact that only elements are able to fire events. This makes my
Models use the window.document element to fire/observe events.
On Tue,
Thanks Tobie! That is a very nice way of doing it.
Many thanks to you and the prototype team for making something, for free,
for everyone to use and putting up us (well, me). :-)
On Tue, Oct 6, 2009 at 9:57 AM, Tobie Langel tobie.lan...@gmail.com wrote:
Jim, Ngan.
This is already possible
I just found out that Event#findElement == Event#element if no arguments are
passed in.
On Mon, Oct 5, 2009 at 8:55 AM, Ngan nganp...@gmail.com wrote:
Hi everyone,
In the new docs, it says that Event#element is deprecated. Is there a
reason for this? The doc says to use Event#findElement
Hi everyone,
In the new docs, it says that Event#element is deprecated. Is there a
reason for this? The doc says to use Event#findElement instead.
However, this doesn't give you the exact element the effect originated
from. Or are we having to go back to using target and srcElement?
Thanks!
Hi, I apologize if this question has been asked before. I've tried
googling for this, but did find a good answer.
What's the best way to have private methods using prototype's
Class.create?
I've tried...
var Worker = Class.create((function() {
function initialize() {
this.someVar = var;
opps, i had typo. return should be:
return {
initialize: initialize,
publicMethod: publicMethod
}
On Sep 10, 9:37 am, Ngan nganp...@gmail.com wrote:
Hi, I apologize if this question has been asked before. I've tried
googling for this, but did find a good answer.
What's the best way
Ah! thank you! sorry for the inconvenience!
On Thu, Sep 10, 2009 at 10:04 AM, T.J. Crowder t...@crowdersoftware.comwrote:
Hi Ngan,
This question is probably more appropriate for the user's group[1],
rather than the core development group. If you'll repost over there,
there are a couple
I'm only having problems with mouseleave (mouseenter doesn't concern
me as much). If an element is resized to be smaller and the mouse is
no longer over the element, the element fails to fire a mouseleave
event. I've tested this in FF 3.5x, Safari 4.0.3, and IE8. IE8 works
properly, but FF and
12 matches
Mail list logo
