[
https://issues.apache.org/jira/browse/TAP5-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644530#action_12644530
]
Howard M. Lewis Ship commented on TAP5-184:
-------------------------------------------
In terms of overrides; my intention was that you could place a "competing"
filter into the pipeline just after the filter being replaced. It would, in
effect, intercept all the calls to the built-in filter ... in other words,
Tapestry's RenderSupport instance would be present, but would never be invoked,
because your custom, Facebook-compatible RenderSupport instance would be the
one visible to the rest of the application during the render.
> Improve error reporting when a javascript asset is intended to be included on
> page which has no <body> element
> --------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-184
> URL: https://issues.apache.org/jira/browse/TAP5-184
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Reporter: Michael Lake
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> I know - silly of me to have a page with no <body></body> element. I spent an
> entire day trying to figure out why the javascript wasn't getting included.
> It was my error, but I can see other people making the same mistake...a
> little error-reporting would be nice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
