[GH-ISSUE #84] Deprecated selector in meteor-api/styles/meteor-color-coding.less #67

Open
opened 2026-05-05 15:01:07 -06:00 by gitea-mirror · 20 comments
Owner

Originally created by @themiguelamador on GitHub (Dec 19, 2016).
Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/84

In meteor-api/styles/meteor-color-coding.less:

Starting from Atom v1.13.0, the contents of atom-text-editor elements are no longer encapsulated within a shadow DOM boundary. This means you should stop using :host and ::shadow pseudo-selectors, and prepend all your syntax selectors with syntax--. To prevent breakage with existing style sheets, Atom will automatically upgrade the following selectors:

  • atom-text-editor::shadow .api.meteor => atom-text-editor.editor .syntax--api.syntax--meteor

  • atom-text-editor::shadow .api.meteor.core => atom-text-editor.editor .syntax--api.syntax--meteor.syntax--core

  • atom-text-editor::shadow .api.meteor.ddp => atom-text-editor.editor .syntax--api.syntax--meteor.syntax--ddp

  • atom-text-editor::shadow .api.meteor.http => atom-text-editor.editor .syntax--api.syntax--meteor.syntax--http

  • atom-text-editor::shadow .api.meteor.template => atom-text-editor.editor .syntax--api.syntax--meteor.syntax--template

  • atom-text-editor::shadow .api.meteor.blaze => atom-text-editor.editor .syntax--api.syntax--meteor.syntax--blaze

  • atom-text-editor::shadow .api.meteor.router => atom-text-editor.editor .syntax--api.syntax--meteor.syntax--router

  • atom-text-editor::shadow .api.meteor.collection => atom-text-editor.editor .syntax--api.syntax--meteor.syntax--collection

  • atom-text-editor::shadow .api.meteor.session => atom-text-editor.editor .syntax--api.syntax--meteor.syntax--session

Automatic translation of selectors will be removed in a few release cycles to minimize startup time. Please, make sure to upgrade the above selectors as soon as possible.

Originally created by @themiguelamador on GitHub (Dec 19, 2016). Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/84 In `meteor-api/styles/meteor-color-coding.less`: Starting from Atom v1.13.0, the contents of `atom-text-editor` elements are no longer encapsulated within a shadow DOM boundary. This means you should stop using `:host` and `::shadow` pseudo-selectors, and prepend all your syntax selectors with `syntax--`. To prevent breakage with existing style sheets, Atom will automatically upgrade the following selectors: * `atom-text-editor::shadow .api.meteor` => `atom-text-editor.editor .syntax--api.syntax--meteor` * `atom-text-editor::shadow .api.meteor.core` => `atom-text-editor.editor .syntax--api.syntax--meteor.syntax--core` * `atom-text-editor::shadow .api.meteor.ddp` => `atom-text-editor.editor .syntax--api.syntax--meteor.syntax--ddp` * `atom-text-editor::shadow .api.meteor.http` => `atom-text-editor.editor .syntax--api.syntax--meteor.syntax--http` * `atom-text-editor::shadow .api.meteor.template` => `atom-text-editor.editor .syntax--api.syntax--meteor.syntax--template` * `atom-text-editor::shadow .api.meteor.blaze` => `atom-text-editor.editor .syntax--api.syntax--meteor.syntax--blaze` * `atom-text-editor::shadow .api.meteor.router` => `atom-text-editor.editor .syntax--api.syntax--meteor.syntax--router` * `atom-text-editor::shadow .api.meteor.collection` => `atom-text-editor.editor .syntax--api.syntax--meteor.syntax--collection` * `atom-text-editor::shadow .api.meteor.session` => `atom-text-editor.editor .syntax--api.syntax--meteor.syntax--session` Automatic translation of selectors will be removed in a few release cycles to minimize startup time. Please, make sure to upgrade the above selectors as soon as possible.
Author
Owner

@halilertekin commented on GitHub (Mar 30, 2017):

+1

<!-- gh-comment-id:290398843 --> @halilertekin commented on GitHub (Mar 30, 2017): +1
Author
Owner

@FaisalJulaidan commented on GitHub (Jun 10, 2017):

+1

<!-- gh-comment-id:307584047 --> @FaisalJulaidan commented on GitHub (Jun 10, 2017): +1
Author
Owner

@ricaragao commented on GitHub (Jun 23, 2017):

+1

<!-- gh-comment-id:310639491 --> @ricaragao commented on GitHub (Jun 23, 2017): +1
Author
Owner

@chriswaalberg commented on GitHub (Jun 26, 2017):

+1

<!-- gh-comment-id:311179361 --> @chriswaalberg commented on GitHub (Jun 26, 2017): +1
Author
Owner

@laddi commented on GitHub (Jun 27, 2017):

+1

<!-- gh-comment-id:311395996 --> @laddi commented on GitHub (Jun 27, 2017): +1
Author
Owner

@amandeepmittal commented on GitHub (Aug 21, 2017):

+1

<!-- gh-comment-id:323726060 --> @amandeepmittal commented on GitHub (Aug 21, 2017): +1
Author
Owner

@OK1BR commented on GitHub (Sep 4, 2017):

+1

<!-- gh-comment-id:326886931 --> @OK1BR commented on GitHub (Sep 4, 2017): +1
Author
Owner

@vioan commented on GitHub (Sep 8, 2017):

+1

<!-- gh-comment-id:328063030 --> @vioan commented on GitHub (Sep 8, 2017): +1
Author
Owner

@abegehr commented on GitHub (Oct 1, 2017):

+1

<!-- gh-comment-id:333384378 --> @abegehr commented on GitHub (Oct 1, 2017): +1
Author
Owner

@t3nshi commented on GitHub (Oct 24, 2017):

+1

<!-- gh-comment-id:339157770 --> @t3nshi commented on GitHub (Oct 24, 2017): +1
Author
Owner

@VioletaCalvo commented on GitHub (Oct 26, 2017):

+1

<!-- gh-comment-id:339684327 --> @VioletaCalvo commented on GitHub (Oct 26, 2017): +1
Author
Owner

@uso212 commented on GitHub (Nov 16, 2017):

+1

<!-- gh-comment-id:345096959 --> @uso212 commented on GitHub (Nov 16, 2017): +1
Author
Owner

@TarekRaafat commented on GitHub (Dec 8, 2017):

+1

<!-- gh-comment-id:350185533 --> @TarekRaafat commented on GitHub (Dec 8, 2017): +1
Author
Owner

@thilakarajk commented on GitHub (Dec 14, 2017):

+1

<!-- gh-comment-id:351719367 --> @thilakarajk commented on GitHub (Dec 14, 2017): +1
Author
Owner

@MartinLorenz commented on GitHub (Dec 18, 2017):

+1

<!-- gh-comment-id:352365906 --> @MartinLorenz commented on GitHub (Dec 18, 2017): +1
Author
Owner

@hanseartic commented on GitHub (Jan 22, 2018):

+1

<!-- gh-comment-id:359428494 --> @hanseartic commented on GitHub (Jan 22, 2018): +1
Author
Owner

@oscrx commented on GitHub (Jan 23, 2018):

+1

<!-- gh-comment-id:359812908 --> @oscrx commented on GitHub (Jan 23, 2018): +1
Author
Owner

@naterkane commented on GitHub (Jan 25, 2018):

+1

<!-- gh-comment-id:360563661 --> @naterkane commented on GitHub (Jan 25, 2018): +1
Author
Owner

@naterkane commented on GitHub (Jan 26, 2018):

this appears to have been fixed here 873e2f72c6 (diff-6cb63e3aeaadc1c240f53ee1f2da43bb)

however I continue to get the deprecation warning in Atom. thoughts?

<!-- gh-comment-id:360801127 --> @naterkane commented on GitHub (Jan 26, 2018): this appears to have been fixed here https://github.com/awatson1978/meteor-api/commit/873e2f72c68554a34be16dc77fff3619df7d565b#diff-6cb63e3aeaadc1c240f53ee1f2da43bb however I continue to get the deprecation warning in Atom. thoughts?
Author
Owner

@naterkane commented on GitHub (Jan 26, 2018):

until @awatson1978 publishes a new version.... you can install the current master branch with

apm install awatson1978/meteor-api

after running the command, restart Atom and all should be fine.

<!-- gh-comment-id:360802789 --> @naterkane commented on GitHub (Jan 26, 2018): until @awatson1978 publishes a new version.... you can install the current master branch with ``` apm install awatson1978/meteor-api ``` after running the command, restart Atom and all should be fine.
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#67
No description provided.