<script> tags for the currently active scripts.
All scripts are obtained from all activated groups on all selected registries.
The scripts are filtered for the given position.
All of the selected scripts are then sorted. First with a default ordering selected to cover the most common cases of scripts following other scripts. Second, a stable topological sort is performed to resolve all the ordering constraints.
The body is invoked with any output discarded. This is to allow nested <wr:activate> and <wr:deactivate> tags.
]]>false).
By default, the application-scope activations and scripts are not included. This is because the application-scope registry is copied to the request, thus without modification during the request, the centrally registered scripts are used.
]]>true).
If missing, the session will not be created.
Session-scope activations are applied after any selected application-scope.
]]>true).
The application-scope registry is copied to the request, thus without modification during the request, the centrally registered scripts and activations are used.
Request-scope activations are applied after any selected application-scope and session-scope.
]]>true).
Page-scope activations are applied after any selected application-scope, session-scope, and request-scope.
]]>true).
]]>registered="true" (the default).
When a group is both activated and deactivate, via these attributes, the activation takes precedence.
Nested <wr:activate> and <wr:deactivate> tags will further refine the activations.
]]>registered="true" (the default).
When a group is both activated and deactivate, via these attributes, the activation takes precedence.
Nested <wr:activate> and <wr:deactivate> tags will further refine the activations.
]]>HEAD_START, HEAD_END,
BODY_START, or BODY_START.
]]><link> tags for the currently active styles.
All styles are obtained from all activated groups on all selected registries.
The styles are filtered for the current request. This filtering is currently limited to the style direction matched to response locale.
All of the selected styles are then sorted. First with a default ordering selected to cover the most common cases of styles overriding other styles. Second, a stable topological sort is performed to resolve all the ordering constraints.
The body is invoked with any output discarded. This is to allow nested <wr:activate> and <wr:deactivate> tags.
]]>false).
By default, the application-scope activations and styles are not included. This is because the application-scope registry is copied to the request, thus without modification during the request, the centrally registered styles are used.
]]>true).
If missing, the session will not be created.
Session-scope activations are applied after any selected application-scope.
]]>true).
The application-scope registry is copied to the request, thus without modification during the request, the centrally registered styles and activations are used.
Request-scope activations are applied after any selected application-scope and session-scope.
]]>true).
Page-scope activations are applied after any selected application-scope, session-scope, and request-scope.
]]>true).
]]>registered="true" (the default).
When a group is both activated and deactivate, via these attributes, the activation takes precedence.
Nested <wr:activate> and <wr:deactivate> tags will further refine the activations.
]]>registered="true" (the default).
When a group is both activated and deactivate, via these attributes, the activation takes precedence.
Nested <wr:activate> and <wr:deactivate> tags will further refine the activations.
]]>