nathan-alden-sr / dom-view-js Goto Github PK

Because JavaScript's property iteration is non-deterministic, any code that relies on context parameters is not guaranteed to work. For example, selector properties with function values and jQuery event property function values can both receive context, which is the current state of the underlying object. However, the current state is non-deterministic because of the JavaScript specification. Some browsers may retain the order as specified in code, but that behavior cannot be relied upon.

http://stackoverflow.com/questions/5525795/does-javascript-guarantee-object-property-order

A developer should be able to return false in init function in order to tell DOMView to ignore that particular selector object. This is useful for optionally adding properties to the view object based on a flag.

Consider the following code:

var view = DomView({
    selector: ".container",
    foo: function (view) {
        view.bar();
    },
    bar: function (view) {
        // view is undefined
    }
});

When foo calls bar, bar is not being provided with the view object.

Custom functions must be evaluated at least once before the DomView function returns. This is because they might create objects that themselves hook to the DOM (e.g., jQuery plugins).

On the following sample:

var view = DomView({
    selector: ".container",
    button: {
        selector: "input[type='button']",
        disable: function (view) {
            this.prop("disabled", true);
            this.attr("value", view.message()); // Calls the wrapper function, not the real function defined below
        }
    },
    message: function () { // Only called once with its return value cached for subsequent wrapper function evaluations
        return "Disabled!";
    }
});

I'm seeing disable and message get executed when the button is "inited". Is this intended behavior?

This is problematic on cases where you're trying to attache a "disable" function to your button while a form is being submitted.