Difference between click and fireEvent

[berlinsurfer]

Hi,
just a short question: is there a difference beween firing the click
event (el.fireEvent('click');) or actually really clicking it ?
Thank you very much in advance,
Jan

[Oskar Krawczyk]

Yes, when you fire the click event, no event properties are being passed - unless you specify them manually - so the following would throw an error:

el.addEvent('click', function(e){

e.stop(); // error here

});

[berlinsurfer]

Thank you very much Oskar.

> - unless you specify them manually -

How would I possibly do that ? I have seen that a script relies on the
event being passed and it's definately easier to generate an event
than to refactor the class...
I have found http://mootools.net/docs/core/Native/Event but which
parameters do I have to use for a simple click event ?
Cheers,
Jan

[Barry van Oudtshoorn]

On 30/08/10 11:42, berlinsurfer wrote:
> How would I possibly do that ? I have seen that a script relies on the
> event being passed and it's definately easier to generate an event
> than to refactor the class...
> I have found http://mootools.net/docs/core/Native/Event but which
> parameters do I have to use for a simple click event ?
> Cheers,
> Jan

The simplest way to do it is to look at the functions that are handling
the click, and create an anonymous object with stubs. That is to say,

blah.fireEvent('click', {
stop: $empty,
preventDefault: $empty,
// etc.
});

--
Barry van Oudtshoorn
www.barryvan.com.au

Not sent from my Apple πPhone.

[אריה גלזר‎]

I'm pretty sure that is why mootools has the Event object:

el.fireEvent('click',new Event);

--

Arieh Glazer
אריה גלזר
052-5348-561
5561

[אריה גלזר‎]

On Mon, Aug 30, 2010 at 7:57 PM, אריה גלזר <arieh....@gmail.com> wrote:

I'm pretty sure that is why mootools has the Event object:

el.fireEvent('click',new Event);

my mistake. I was sure i read somewhere how this can be used but couldn't find the source, and playing with it made me realize Event requires an event as an argument. Any insight from the masters?

[Sanford Whiteman]

> my mistake. I was sure i read somewhere how this can be used but couldn't
> find the source, and playing with it made me realize Event requires an event
> as an argument. Any insight from the masters?

http://jsfiddle.net/gCgXq/2/

Note Event ctor doesn't need a real event in IE.

-- S.

[אריה גלזר‎]

Very Cool. I Think I'll implement this and upload to the Forge (Event.Mock?)

[אריה גלזר‎]

And it's done!

I must say the MDC event spec has a lot of potential. It actually supports bubbling. A shame this cannot be easily implemented on IE, or we could have had a very strong fireEvent implementation...

[Rolf -nl]

In what kind of real user case would you need this? When you must act
like you actually clicked a link (or whatever element that has a click
event attached) when you didn't?

On Aug 31, 8:10 am, אריה גלזר <arieh.gla...@gmail.com> wrote:
> And it's done <http://mootools.net/forge/p/event_mock>!

[Sanford Whiteman]

> In what kind of real user case would you need this? When you must
> act like you actually clicked a link (or whatever element that has a
> click event attached) when you didn't?

When you are using a third-party (or inalterable for some other
reason) event handler that expects an Event to be passed and doesn't
create its own mock `e` internally when it's been fake-fired. IOW,
when you want to fire an event handler that depends on an event (even
though the two could/should be separate).

You can fake a duck-typed Event, as Barry suggested, by adding the
minimal props to a simple Object, but this requires inspecting the
handler code in depth and could be really annoying to maintain. Pass
it a real Event and you shouldn't need to worry about faking anything.

-- S.