More on this... it appears that the problem is in a filter block in my
top level autohandler. This filter is designed to disable all
submit buttons on the way out - they then get enabled as part of an
onload handler. This way my users can't submit a page before I am
done populating it. However, this appears to cause Mason (1.32 at
least) to refuse to pass on the output even when flush_buffer is
called. It seems to accumulate all output until the component
completes, then send everything. Is that the expected behavior?
Here's the filter block, just in case that matters:
<%filter>
s{input ([^>]*?type=")(submit|reset)(".*?>)}{input disabled="disabled" $1$2$3}isg ;
</%filter>
Help?
--
Shane McCarron
[EMAIL PROTECTED]
- [Mason] flush_buffer and apache 2 / mod_perl 2 Shane McCarron
- [Mason] Re: flush_buffer and apache 2 / mod_perl 2 Shane McCarron
- Re: [Mason] Re: flush_buffer and apache 2 / mod_pe... Shane McCarron

