Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #7271
Proposed Changes
The problem was the styles that come from wp core, or Gutenberg or the themes (not referring to the theme specific CSS we have) were still getting loaded with priority 10. So these core/gb/other styles were also overriding our LM styles if the specificity was same.
For example, in this particular instance with site icon, we have a style to set the width of site logo to auto, in core the width for that is 120px. So core style was overriding ours.
We could just remove the priority 9, but that'd have removed the added facility we got, which is overriding base lm styles with theme specific LM styles.
To still have that facility, we removed the 9, but added 11 to the theme specific styles. Now our base LM styles overrides the core styles, and our theme specific styles override the base LM styles.
Also, there was additional call to Course theme's enqueue function from divi's PHP file. We've removed that.
Before increasing priority:
After increasing priority:
Testing Instructions
learning-mode.css
filePre-Merge Checklist