Problem with nested code + tag + colons in LESS
See original GitHub issueCssComb is continuing indenting when the following code occurs:
.list {
overflow-y: auto;
button::-moz-focus-inner {
padding: 0;
}
.row {
position: relative;
}
.row1 {
overflow: hidden;
}
}
As far as I was able to debug, this happens when there is a tag followed by a double colon (:😃. If you place the tag with a class it’s fine. Was this issue address before? Is there some setting I can change to avoid this happening?
<bountysource-plugin>
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Issue Analytics
- State:
- Created 9 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
vue.js - How to solve "semi-colon expected" warnings (css ...
The recommended way to solve this is by making use of the Stylelint extension to handle your CSS linting (& SCSS and/or Less,...
Read more >Question about nested html tags | Codecademy
So the actual question would be: are those three ways of tag nesting well written? Is there something wrong with the SCT? Thank...
Read more >Code blocks missing margin-top when nested in definition lists ...
An alternative that displays well but results in less meaningful HTML markup is to treat the nested code block as a separate definition....
Read more >CSS Basics: The Syntax That Matters & The Syntax That Doesn't
In the braces section, you say a colon is invalid as part of a selector, but it isn't as it's used for pseudoclasses....
Read more >Error Explanations for The W3C Markup Validation Service
Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed...
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 FreeTop 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
Top GitHub Comments
This seems to fixed in the latest csscomb release 🕺
I’m having the same issue. Is there a work around?