You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configure as "_isCompletionIndicatorEnabled": false
Inspect display style of component-title-inner
Expected behaviour
Expecting that the default style display: block is retained when "_isCompletionIndicatorEnabled": false
Expecting that the extension style display: inline-block is used only when needed, when "_isCompletionIndicatorEnabled": true
Actual behaviour
The style display: inline-block is applied to all simply by installing the extension.
What impact does this have? On occasion some visual elements need to occupy the same space (e.g., component-title-inner) as the progressbar wants to. Doesn't seem to make sense to have PLP styles interfering when it is not being enabled. Also makes it more difficult to upgrade older courses.
Would prefer a strategy that applies the inline-block style only when the Completion Indicator is enabled.
The text was updated successfully, but these errors were encountered:
pageLevelProgressIndicator.less overrides Adapt default display style even when
"_isCompletionIndicatorEnabled": false
I'm running:
Steps to reproduce
"_isCompletionIndicatorEnabled": false
Expected behaviour
display: block
is retained when"_isCompletionIndicatorEnabled": false
display: inline-block
is used only when needed, when"_isCompletionIndicatorEnabled": true
Actual behaviour
The style
display: inline-block
is applied to all simply by installing the extension.What impact does this have? On occasion some visual elements need to occupy the same space (e.g., component-title-inner) as the progressbar wants to. Doesn't seem to make sense to have PLP styles interfering when it is not being enabled. Also makes it more difficult to upgrade older courses.
Would prefer a strategy that applies the inline-block style only when the Completion Indicator is enabled.
The text was updated successfully, but these errors were encountered: