[GH-ISSUE #18] Style elements within text editors using the atom-text-editor::shadow selector or the .atom-text-editor.less file extension.If you want to target overlay elements, target them directly or as descendants of atom-overlay elements. #14

Closed
opened 2026-05-05 14:58:17 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @bthusby on GitHub (Feb 21, 2015).
Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/18

In stylesheets/meteor-color-coding.less: Style elements within text editors using the atom-text-editor::shadow selector or the .atom-text-editor.less file extension.
If you want to target overlay elements, target them directly or as descendants of atom-overlay elements.

Originally created by @bthusby on GitHub (Feb 21, 2015). Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/18 In stylesheets/meteor-color-coding.less: Style elements within text editors using the `atom-text-editor::shadow` selector or the `.atom-text-editor.less` file extension. If you want to target overlay elements, target them directly or as descendants of `atom-overlay` elements.
Author
Owner

@asaheed commented on GitHub (Feb 24, 2015):

same here

<!-- gh-comment-id:75749411 --> @asaheed commented on GitHub (Feb 24, 2015): same here
Author
Owner

@briannhinton commented on GitHub (Feb 24, 2015):

I'm seeing it as well. I'm wondering if this is a false positive as seen here:
https://github.com/atom/editor-stats/issues/16

Since I see the .less file has the atom-text-editor used for styling.

<!-- gh-comment-id:75766634 --> @briannhinton commented on GitHub (Feb 24, 2015): I'm seeing it as well. I'm wondering if this is a false positive as seen here: https://github.com/atom/editor-stats/issues/16 Since I see the .less file has the atom-text-editor used for styling.
Author
Owner

@brylie commented on GitHub (Mar 27, 2015):

This has been reported many times now. FWIW, I created an issue on Atom requesting that the Deprecation cop check for duplicate issues before creating new.

<!-- gh-comment-id:86900173 --> @brylie commented on GitHub (Mar 27, 2015): This has been reported many times now. FWIW, I created an issue on Atom requesting that the [Deprecation cop check for duplicate issues before creating new](https://github.com/atom/atom/issues/6120).
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/meteor-api#14
No description provided.