dashorst opened a new issue, #1959: URL: https://github.com/apache/wicket/issues/1959
`TransparentWebMarkupContainer` lets components that were added to its parent appear in the markup inside it, without being added to the container itself. It is handy, for example to add a CSS class to the `<html>` or `<body>` tag without moving every component into a new container, but few developers know it exists: its Javadoc is short and the user guide doesn't mention it. ## Where - `wicket-core/src/main/java/org/apache/wicket/markup/html/TransparentWebMarkupContainer.java`, the class Javadoc, which is currently one line: `A simple "transparent" markup container.` - The user guide, in `wicket-user-guide/src/main/asciidoc`. A natural place is the chapter on layout and markup inheritance (`layout/`) or the one on controlling HTML (`keepControl/`). The appendix `contributing.adoc` explains how to build the guide locally. ## Done when - The Javadoc says what the container does, when to use it, and its limits (for example how it behaves with Ajax updates of its children, and with borders and markup inheritance — check the code and tests for what is true). - The guide has a short section with an example, such as the `<body>` CSS-class case. ## Background Originally requested as [WICKET-7171](https://issues.apache.org/jira/browse/WICKET-7171). --- Part of #1945. This issue is meant for a first contribution to Wicket. To work on it, leave a comment so others know; a claim without a pull request lapses after two weeks. Questions are welcome, here on the issue or on [email protected]. Start your branch from `master`, and see [Send a pull request to Wicket](https://wicket.apache.org/contribute/wicket-pull-request.html) for building and testing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
