Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Inconsistent Form.Request behavior when passing null for 'update' parameter #1055

ericcholis opened this Issue Oct 26, 2011 · 0 comments


None yet
1 participant

There is inconsistent behavior between browsers when passing null to the 'update ' parameter to a new Form.Request. Using Core 1.4.1 with compatibility and More

Sample Code:

new Form.Request(document.id('someForm'),null,{
  onComplete:function(target, tree, elements, html, javascript){

In Firefox 7 the null parameter gets ignored and the Form.Request behavior performs as expected. In Chrome and Internet Explorer, a TypeError exception is thrown. Specifically at the following line of code in the this.Events.addEvent function:

this.$events[type] = (this.$events[type] || []).include(fn);

The error originates with the following gist, which adds Object.watch() functionality for browsers that do not support it:

Closing this ticket, since this isn't a MooTools issue directly

@ericcholis ericcholis closed this Oct 26, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment