Container heading level settings do not work
Container headers do not work when when heading level settings are configured within section rule forms.
Steps to Reproduce
Set the container heading level dropdown to a specific value. The runtime output in the UI is the same despite selecting different values.
An issue in the application skin.
Perform the following local-change:
- Open the skin definition.
- Open the container definition (Default container in this use case).
- Select the 'Use the skin's base settings for text styling' checkbox. This overrides the format. The value which is set from the section in the Heading level get preference.
- Add pyEndUser skin in inheritance.
The above steps are displayed in the images below.
Open the Properties panel to determine which container is used. Here, the Default container is used.
Open the application skin, (CPMML6). Navigate to the Inheritance tab and add pyEndUser skin.
Navigate to Component Styles tab and select the Container type. Open the definition for the Default container.
Select the 'Use the skin's base settings for text styling' checkbox.
Note: If the checkbox is not checked, two options display as below, one for Collapsed Text and the other for Expanded Text (these options do not display if the checkbox is selected as indicated in Step 3). By default, both are use Heading 2 as a mixin and this takes precedence over the section heading configurations.
0% found this useful