So, you just added a new Map to all markup containers that keeps components in it?  Why would you do that?

We already have a storage mechanism for children of a markup container. Why do we need two storage containers for children? Why can't you call add(foo) and get("fooID")?

Oh, so all that's left is to do all the real work?  :)

Like I mentioned in my previous response on this thread - you need to come to us with everything you've got.  It needs to show us:

  - a real working solution   - something that doesn't break existing stuff (real world apps, and   passes all existing test cases)   - test cases for itself and all new functionality   - proof that it doesn't allow the designers to easily break security   (like Igor's example)

Then you come with a "patch" that simply adds a bloated second place to store children in all markup containers?  That's not helping your case.

If you can truly present an elegant solution that solves all of the above, we can consider it. Do yourself the favor of really working through the solution wholeheartedly.