Esto es lo que yo uso: http://jsfiddle.net/mendesjuan/rHMCy/4/
actualizado para trabajar con IE9 +
/**
* Fire an event handler to the specified node. Event handlers can detect that the event was fired programatically
* by testing for a 'synthetic=true' property on the event object
* @param {HTMLNode} node The node to fire the event handler on.
* @param {String} eventName The name of the event without the "on" (e.g., "focus")
*/
function fireEvent(node, eventName) {
// Make sure we use the ownerDocument from the provided node to avoid cross-window problems
var doc;
if (node.ownerDocument) {
doc = node.ownerDocument;
} else if (node.nodeType == 9){
// the node may be the document itself, nodeType 9 = DOCUMENT_NODE
doc = node;
} else {
throw new Error("Invalid node passed to fireEvent: " + node.id);
}
if (node.dispatchEvent) {
// Gecko-style approach (now the standard) takes more work
var eventClass = "";
// Different events have different event classes.
// If this switch statement can't map an eventName to an eventClass,
// the event firing is going to fail.
switch (eventName) {
case "click": // Dispatching of 'click' appears to not work correctly in Safari. Use 'mousedown' or 'mouseup' instead.
case "mousedown":
case "mouseup":
eventClass = "MouseEvents";
break;
case "focus":
case "change":
case "blur":
case "select":
eventClass = "HTMLEvents";
break;
default:
throw "fireEvent: Couldn't find an event class for event '" + eventName + "'.";
break;
}
var event = doc.createEvent(eventClass);
event.initEvent(eventName, true, true); // All events created as bubbling and cancelable.
event.synthetic = true; // allow detection of synthetic events
// The second parameter says go ahead with the default action
node.dispatchEvent(event, true);
} else if (node.fireEvent) {
// IE-old school style, you can drop this if you don't need to support IE8 and lower
var event = doc.createEventObject();
event.synthetic = true; // allow detection of synthetic events
node.fireEvent("on" + eventName, event);
}
};
Tenga en cuenta que llamar fireEvent(inputField, 'change');
no significa que en realidad va a cambiar el campo de entrada. El caso de uso típico para disparar un evento de cambio es cuando configura un campo mediante programación y desea llamar a los controladores de eventos ya que al llamar al input.value="Something"
no se activará un evento de cambio.
NB esto es para el propósito de prueba rápida. Para una solución de navegadores cruzados más robusta, compatible con estándares, consulte la respuesta de Juan. –
No entiendo el ciclo y esto no funcionó en el dispositivo móvil. –
@im_benton: El ciclo era para las necesidades específicas de OP. Si sólo necesita para desencadenar un evento de clic, se puede omitir la línea que comienza con 'por ('. – rinogo