> ...you wanted consistent "header" and "footer" boilerplate on all pages, with generated or otherwise external content in between.
That's essentially correct. > There are a number of ways to accomplish that, depending on how much scripting effort you're willing to invest. As far as I'm concerned the issue isn't isn't whether or not it's possible, but rather as you suggest, a matter of investment. > It isn't clear to me that using an <iframe> to "embed" content in a static page was the best way, although it may have been the easiest. I don't think anybody is arguing that the current design is necessarily "the best way." That said, it certainly was (and is) easy. > Web-hostile techniques usually are. We can blame Microsoft for that! I'm no fan of Microsoft, but I don't think they had any part in the original development of frames. From what I recall, frames came about in the mid-to-late 90s as a way to improve site layout and they were all the rage back then. However, they fell out of common use as table-based and then CSS-based designs supplanted them. Justin On Tue, Feb 25, 2025 at 1:13 AM Arjun Ray <ara...@gmail.com> wrote: > On Tue, 25 Feb 2025 00:09:21 -0600, Justin Bertram > <jbert...@apache.org> wrote: > > | The current design did not, in fact, *intend* to prevent that. > > Fair enough. > > | It was an unfortunate consequence of a compromise which I referenced > | in my previous email on this thread. However, I digress. > > If I understand this correctly, you wanted consistent "header" and > "footer" boilerplate on all pages, with generated or otherwise > external content in between. > > There are a number of ways to accomplish that, depending on how much > scripting effort you're willing to invest. It isn't clear to me that > using an <iframe> to "embed" content in a static page was the best > way, although it may have been the easiest. (Web-hostile techniques > usually are. We can blame Microsoft for that! :-)) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org > For additional commands, e-mail: dev-h...@activemq.apache.org > For further information, visit: https://activemq.apache.org/contact > > >
