-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content-aware component containers #156
Comments
it seems that client-side nodes cannot be passed to server-side (causing an error about endless recursion); this means that the first implementation will just report that there have been changes to the dom and nothing else a simple workaround for finding objects on the server would be to register them with content-aware before they are physically added (e.g. by setting a property of that new object, getting it on the client and then passing that to the server) - this defeats the purpose of content awareness, though maybe there exists a better way? it seems near impossible to figure out a server-side object from a client-side component, but perhaps I am missing something? |
feedback from users (if any ever) will decide how the feature will be developed further
Create component(s) that fire events when something is added or removed to them, regardless of the level of nesting.
Use case: a layout into which components are added should fire events when something has been added or removed from it.
Mutation observers seem to be a good approach, as detailed in https://stackoverflow.com/questions/2844565/is-there-a-javascript-jquery-dom-change-listener
The text was updated successfully, but these errors were encountered: