Forums

I have discovered after I got my example from a previous post working (viewtopic.php?p=32873), another problem. This may be a "feature" and not a "bug", but it seems like it's more of a bug to me.

In order for a Y.View to bind to it's container (if the container is already an existing DOM element), the 'container' attribute must be accessed using the attribute getter first.

My use of Y.View might be somewhat unconventional since I am creating a logical view rather than constructing a new DOM element sub-tree, so this might not have come up in testing or traditional use.

This example is working, but only because I have put a "this.get('container')" into the render() method. If I comment this out, the DOM events described in "events:" do not fire (or bind, I am assuming):

http://www.0x743.com/view-event-3.5.1.html

I discovered this because when debugging, I put an alert to give me the contents of the container. When I'd do that, the event would be heard and the proper handler would fire. When I commented out the alert, it would not work.

Upon further investigation, I determined that if I did a this.get('container') or myInstance.get('container') - even without the alert, the events would be handled properly.

This might be reasonable behavior if you're creating and appending a DOM subtree to the main DOM, but if you're attaching to an existing DOM element it's not; even if it could be argued that it's reasonable behavior, it is unexpected (inconsistent) and I couldn't find it documented anywhere.

Thanks!
Brett

I am attaching the View to an existing node rather than creating one. The reason is because the client side templating is way to slow for my application.

So, when I attach to an existing DOM node rather than create one just for the View, I find that I have to make an attribute call to 'container' before the events described in "events:" are bound to the 'container'.

if I create a new DOM node just for the View, I have to make no such "get" call to 'container'.

Make sense?

See my example.

Brett

This is pretty odd. I'm able to reproduce your use case and like you say, I have to call the get container attribute in order for the events to bind to the view. How odd...

Sorry I can't be of help.

There is currently a ticket open for this:
http://yuilibrary.com/projects/yui3/ticket/2532304

Feel free to add your comments/CC yourself on it.