Add ngeo scope to CSS classes
See original GitHub issueCSS class names used in ngeo are not enough scoped and thus will cause conflicts.
For example, for the search directive, we use the class “.search” and the CSS defines a rule like:
.search input {
height: 100%;
}
This conflicts with any application or component using an input
in a search
class.
As a consequence, ngeo classes should be prefixed like this:
.ngeo-search input {
height: 100%;
}
Issue Analytics
- State:
- Created 7 years ago
- Comments:21 (21 by maintainers)
Top Results From Across the Web
scope - CSS: Cascading Style Sheets - MDN Web Docs
The :scope CSS pseudo-class represents elements that are a reference point for selectors to match against.
Read more >Scope of CSS class - html - Stack Overflow
It takes the style of the stylesheets added latest in your html . Try placing your stylesheet link at the very top.
Read more >Saving the Day with Scoped CSS
To get Scoped CSS working I simply add a little bit of logic to content.php and content-single.php to look for the custom field...
Read more >Scope Reference — highlight.js 11.7.0 documentation
Some scope names above have a . in them. We use this notation to specify sub-scopes. In the generated HTML this will output...
Read more >Use CSS to Style the Experience - PTC Support
1. Click Application under STYLES. · 2. Now that the CSS classes have been added to the application styles, you can add them...
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
@gberaudo or @sbrunner I would like to clarify my intentions. Please, let me know if you agree.
First, anything that’s part of GeoMapFish should have a
gmf-
prefix instead ofngeo-
.Also, any class that is defined alongside a directive definition should simply be removed and the definition should use the tag name instead. For example, the
.search
class name is used here:And the definition currently looks like this (in the .less files):
Could be changed like this:
What do you think ?
Many thanks @adube