Global Styles: enqueue styles later so theme css can load first #34147
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.
Description
Deenqueues and deregisters the 'global-styles' asset enqueued by Core, and reenqueues it on a later priority.
This allows theme css enqueued on the default priority to load first, so that a user's Global Style settings take precedence over theme css (particularly in the case of equal css selector weight).
Fixes #34141
Example of conflicts with themes: Automattic/themes#4435
How has this been tested?
Ensure that Global styles is loaded after the theme css on the page.
Screenshots
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist:
*.native.js
files for terms that need renaming or removal).