jreades is right. You are going to end up in an endless loop if you do it the way to are now. If the frameset page is the autohandler for the main component, the "frame src" tag will cause the browser to fetch the component from the server again which will invoke the same autohandler, and keep embedding frames inside frames ad infinitum.

So don't try to do framesets (client-side) as a mason autohandler (server-side).

If you must use framesets, then forget the autohandler for a moment, because the client needs to fetch the frameset separately from any embedded frames. So your referring link will need to point to the frameset, and the "frame src" tags will link the the content pages, which should NOT inherit from the frameset page.

In reply to Re: HTML::Mason and Frames by sharkey
in thread HTML::Mason and Frames by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.