SOLVED
Design Header and Footer components that are drag and drop
We're all in agreement that it's a terrible practice, but as I said in the original post, it is a MANDATE. I've spent a lot of time explaining to management that it isn't a best practice and goes against the conventions of what I've seen, but I don't yet have the experience to lay out any major problems that it might cause, so I've been told by folks in my management chain that the headers and footers have to use drag and drop, and that they should be "smart enough" to figure out where to position themselves on the page. In my humble opinion, it's not worth the extra effort, time/cost it will take to build in that intelligence, (because it doesn't yield any real benefit that I can see), but at this point, I MUST go ahead and do it the way I'm told to do it unless I can come up with some ironclad reasons not to, (i.e. problems it will eventually cause). At this point, I have to stop debating, and just go ahead and build what I've been asked to build.
I guess I could have the component evaluate the page, and then render itself right before the closing </html>, (for the footer), and have the header, render itself right after the opening <html>, and before the <body> etc? Can I use the DOM, or is there some other way to build intelligence into the component so that it renders in the correct section of the page? Can anyone think of a way to do this? I'll continue to try to show why it's best to follow the established best practices, but in the meantime, I've got to find a way to implement the way it's been specified by those who sign my checks. 
Related Conversations
