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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
based on the automatic upgrade rule, it should probably just be changed to
atom-text-editor.editor .git-blame-mount,instead of deletedThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only reverence I can find related to removing shadow dom is http://flight-manual.atom.io/shadow-dom/sections/removing-shadow-dom-styles/#shadow
By that section there is no recommendation to add
.editor. The line that is removed is comes before the current correct line.If you have an additional reference I will be glad to take a look at that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original issue shows the automatic translation that atom will do. It's a little hard to see in the way it was reported, but they have the original shadow form of the selector followed by
=>and then the automatically transpiled version. Per the docs you are correct, though they do reference it down here: http://flight-manual.atom.io/shadow-dom/sections/removing-shadow-dom-styles/#i-followed-the-guide-but-now-my-styling-is-brokenIt is a bit unclear which is preferred, but since it was automatically adding the
.editorbefore it is fully deprecated, I think it would be good to keep that as an option for ensuring specificity is high (though I doubt that there would be a conflict with.git-blame-mount)