Increase specificity of Output styles #9496
Merged
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.
Signed-off-by: Gabriel Bodeen gabriel.bodeen@ericsson.com
What it does
Fixes #9110.
As noted in a comment on the issue, git-bisect shows the regression was introduced in this commit, part of the PR where
@theia/monaco-editor-core
was upgraded from 0.19.0 to 0.20.0.The cause is that in the upgraded Monaco, the editor token colors stylesheet is lazy-loaded and only attached to the DOM after the first editor is attached. So the CSS classes affecting the output are now loaded in the reverse order to what was originally expected.
The upstream fix is included as of v0.21.x, so if a PR such as this one going to 0.23.x is merged it will resolve the problem.
In the meantime, the immediate problem in the Output package can be resolved simply by increasing the specificity of the CSS selector, and it will not need to be reverted after a Monaco upgrade.
How to test
View > Output
in the menus to open the Output widget if it is not visible. In the dropdown output channel list, selectAPI Sample: my test channel
.master
where you'll currently see:Review checklist
Reminder for reviewers