在更新到版本 1.7.3 后，原型事件注册表似乎存在问题。我正在使用 prototype_event_registry 访问元素存储上的点击事件，以便我可以重放它们。
这样我就可以停止事件并根据回调选择性地恢复它们。一切都运行良好，但在查看 1.7.0 和 1.7.3 差异后，它似乎已经被移除了？
我知道这是内部实现，可能不应该在第一时间使用它。无论如何，我的问题是：
我已将代码更新为与 1.7.3 兼容，但对我来说似乎非常卑劣，是否有更好的方法来做到这一点？
/**
* creates a toggling handler for click events taking previous click events into account.
*
* w.r.t stopping of a click event, handles cases where the button is a submit or a normal button.
* in the case of a submit, calling <tt>Event.stop()</tt> should be sufficient as there are no other listeners on the button.
* however, if a normal button has a handler that calls <tt>save()</tt>, and another handler using client code and calling stop,
* it will not affect stopping of the event, since <tt>Event.stop</tt> only stops propagation, not other handlers!
*
* note that this function will always execute the specified handler before any other defined events.
*
* @param {Element} element the element to use for this click event
* @param {Function} handler the handler to use for this stopping click event, if this handler returns true,
* all other actions for the click event will be prevented
* @returns {Element} the element that was supplied as argument
*/
function stoppingClickEvent(element, handler) {
if (!element) throw 'cannot use method, if element is undefined';
// assign default handler if none was supplied
handler = handler || Prototype.emptyFunction;
if (element.type && element.type === 'submit') {
element.on('click', function(submitEvent) {
// call the supplied handler with the current element as context and the event as argument
// if it returns true, we should stop the event
var stopEvent = handler.call(element, submitEvent);
if (stopEvent) {
// since the element's default action will be to submit a form, we prevent it
submitEvent.stop();
}
});
} else {
// prototype 1.7.3 removed support for 'prototype_event_registry', so we need to do multiple hacks here
// first get the window of the element so we can access the prototype
// event cache from the correct context (frames)
var elementDoc = element.ownerDocument;
var elementWindow = elementDoc.defaultView || elementDoc.parentWindow;
if (!elementWindow) {
throw 'cannot access the window object for element ' + element.id;
}
// we are dealing with a normal element's click event, so we don't know how many click events have been set up.
// capture them all so we can decide to call them or not.
// FIXME: need a better way of doing this
var registry = elementWindow['Event'].cache[element._prototypeUID || element.uniqueID] || {},
events = registry['click'] || [];
// now that we have a copy of the events, we can stop them all and add our new handler
element.stopObserving('click').on('click', function(clickEvent) {
// call the supplied handler with the current element as context and the event as argument
// if it returns true, we should stop the event
var stopEvent = handler.call(element, clickEvent);
if (!stopEvent) {
// the event should not be stopped, run all the original click events
events.each(function(wrapper) {
wrapper.handler.call(element, clickEvent);
});
}
});
}
return element;
}
Event.cache对象被设置为防止一些内存泄漏并提高性能。我非常确定任何扩展元素上都应该存在element._prototypeUID，但除此之外，这将是引用每个元素的事件注册表的方式。 - Geek Num 88