[
https://issues.apache.org/jira/browse/WICKET-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ertl reopened WICKET-549:
-------------------------------
Using the <html> as a wicket component seems to swallow certain header
contributions...
Simply add any ajax component (like AjaxLink) and see that the inclusion of
ajax-event.js (or anything else) will be missing once you attach a
WebMarkupContainer to <html>.
--markup--
<html wicket:id="html">
...
</html>
--java--
Page#add(new WebMarkupContainer("html"))
--effect--
header contributions are missing :-(
> <html> should be accessible in wicket
> -------------------------------------
>
> Key: WICKET-549
> URL: https://issues.apache.org/jira/browse/WICKET-549
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Peter Ertl
> Assigned To: Juergen Donnerstag
> Fix For: 1.3
>
>
> --- issue copy-pasted from mailing list ---
> On 5/9/07, Peter Ertl <[EMAIL PROTECTED]> wrote:
> Hi folks,
> I try to setup a multi-language website like that:
> <? xml version= "1.0" encoding ="UTF-8" ?>
> <! DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "
> http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
> <html wicket:id="html" xmlns:wicket xmlns=" http://www.w3.org/1999/xhtml";
> xmlns:lang=[current language] lang=[current language]>
> ....
> However, accessing <html> using a wicket:id will fail:
> org.apache.wicket.WicketRuntimeException: Programming
> error: 'parent' should be a Page or a Border.
> changing the tag using a MarkupFilter will also fail as it requires to
> value of the current locale of WebSession
> but the markup filter seems to allow no access to it.
> It would be straightforward to just access html using a wicket:id...
> *imho* this would be a great enhancement!
> Can somebody think of a better solution?
> On 5/9/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> hmm this is because of the HtmlHeaderContainer that container wants a page
> to be its parent.
> So you can't attach a wicket container to the html because then you
> encapsulate the complete page.
> i dont know immediantly how to solve this
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
