TextMate scope selectors: child combinator is not implemented
See original GitHub issueSelectors such as "scope1 > scope2"
aren’t working.
Expected behavior:
it should select all scope2
elements that are the direct children of scope1
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Direct children (Child combinator) selector not restricting to ...
Note: This property is applied to list items, i.e. elements with display: list-item; by default this includes <li> elements. Because this ...
Read more >Child combinator - CSS: Cascading Style Sheets | MDN
The child combinator (>) is placed between two CSS selectors. It matches only those elements matched by the second selector that are the ......
Read more >Ecmascript Syntax - Package Control
Ecmascript Sublime Syntax · Remaining Work · Why Bother · Feature Coverage · Non-JS extensions · SublimeText Symbols · Themes · Scopes ·...
Read more >PDF - Springer Link
A CSS rule is applied using selectors followed by one or more declarations, ... This is why a property is applied to all...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@alexdima To be honest i found out about this selector quite recently, but the changelog says it was introduced in 2012.
@jeff-hykin AFAIK
>
did not exist when we first wrotevscode-textmate
. I cannot find any mention of it at https://macromates.com/manual/en/scope_selectorsHowever, with TextMate 2.0, it appears that they appear in the scope selector grammar at https://macromates.com/textmate/manual/references#scope-selector