Overriding style that already has !important
If I want to override some css from my component child, I just use:
:host ::ng-deep .y {
x: !important;
}
but how to override a style that already has !important? The above example in this case won't work
angular
add a comment |
If I want to override some css from my component child, I just use:
:host ::ng-deep .y {
x: !important;
}
but how to override a style that already has !important? The above example in this case won't work
angular
3
You would have to make the CSS selector more specific. Can you show the HTML markup of the element and the context around it? If you could make a stackblitz showing the problem, that would be even better.
– ConnorsFan
Nov 22 at 14:19
The original style: .sortable-container .sortable-list .active I tried: body .sortable-container .sortable-list li.active
– Kamil Kamil
Nov 22 at 14:40
add a comment |
If I want to override some css from my component child, I just use:
:host ::ng-deep .y {
x: !important;
}
but how to override a style that already has !important? The above example in this case won't work
angular
If I want to override some css from my component child, I just use:
:host ::ng-deep .y {
x: !important;
}
but how to override a style that already has !important? The above example in this case won't work
angular
angular
edited Nov 22 at 14:21
marc_s
570k12811001250
570k12811001250
asked Nov 22 at 14:15
Kamil Kamil
184
184
3
You would have to make the CSS selector more specific. Can you show the HTML markup of the element and the context around it? If you could make a stackblitz showing the problem, that would be even better.
– ConnorsFan
Nov 22 at 14:19
The original style: .sortable-container .sortable-list .active I tried: body .sortable-container .sortable-list li.active
– Kamil Kamil
Nov 22 at 14:40
add a comment |
3
You would have to make the CSS selector more specific. Can you show the HTML markup of the element and the context around it? If you could make a stackblitz showing the problem, that would be even better.
– ConnorsFan
Nov 22 at 14:19
The original style: .sortable-container .sortable-list .active I tried: body .sortable-container .sortable-list li.active
– Kamil Kamil
Nov 22 at 14:40
3
3
You would have to make the CSS selector more specific. Can you show the HTML markup of the element and the context around it? If you could make a stackblitz showing the problem, that would be even better.
– ConnorsFan
Nov 22 at 14:19
You would have to make the CSS selector more specific. Can you show the HTML markup of the element and the context around it? If you could make a stackblitz showing the problem, that would be even better.
– ConnorsFan
Nov 22 at 14:19
The original style: .sortable-container .sortable-list .active I tried: body .sortable-container .sortable-list li.active
– Kamil Kamil
Nov 22 at 14:40
The original style: .sortable-container .sortable-list .active I tried: body .sortable-container .sortable-list li.active
– Kamil Kamil
Nov 22 at 14:40
add a comment |
2 Answers
2
active
oldest
votes
Try this
:host /deep/ .y
instead of
:host ::ng-deep .y
I use :host /deep/ .y in my Angular application and works perfectly
2
::ng-deep, /deep/ and >>> are deprecated.
– Jai
Nov 22 at 14:28
angular.io/guide/component-styles#deprecated-deep--and-ng-deep
– Jai
Nov 22 at 14:31
This doesnt help :(
– Kamil Kamil
Nov 22 at 14:36
add a comment |
Going from your comment about the original code this should probably work:
:host ::ng-deep .sortable-container .sortable-list ul .active {
x: value !important;
}
This assumes you're in a 'ul' but it could be ol or dl and replaced just as easily.
Don't forget theliinli.active.
– ConnorsFan
Nov 22 at 15:22
He shouldn't need it. The ul is an inserted element above the .active so it is more specific.
– rrd
Nov 22 at 15:23
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432895%2foverriding-style-that-already-has-important%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try this
:host /deep/ .y
instead of
:host ::ng-deep .y
I use :host /deep/ .y in my Angular application and works perfectly
2
::ng-deep, /deep/ and >>> are deprecated.
– Jai
Nov 22 at 14:28
angular.io/guide/component-styles#deprecated-deep--and-ng-deep
– Jai
Nov 22 at 14:31
This doesnt help :(
– Kamil Kamil
Nov 22 at 14:36
add a comment |
Try this
:host /deep/ .y
instead of
:host ::ng-deep .y
I use :host /deep/ .y in my Angular application and works perfectly
2
::ng-deep, /deep/ and >>> are deprecated.
– Jai
Nov 22 at 14:28
angular.io/guide/component-styles#deprecated-deep--and-ng-deep
– Jai
Nov 22 at 14:31
This doesnt help :(
– Kamil Kamil
Nov 22 at 14:36
add a comment |
Try this
:host /deep/ .y
instead of
:host ::ng-deep .y
I use :host /deep/ .y in my Angular application and works perfectly
Try this
:host /deep/ .y
instead of
:host ::ng-deep .y
I use :host /deep/ .y in my Angular application and works perfectly
answered Nov 22 at 14:23
Mile Mijatovic
905923
905923
2
::ng-deep, /deep/ and >>> are deprecated.
– Jai
Nov 22 at 14:28
angular.io/guide/component-styles#deprecated-deep--and-ng-deep
– Jai
Nov 22 at 14:31
This doesnt help :(
– Kamil Kamil
Nov 22 at 14:36
add a comment |
2
::ng-deep, /deep/ and >>> are deprecated.
– Jai
Nov 22 at 14:28
angular.io/guide/component-styles#deprecated-deep--and-ng-deep
– Jai
Nov 22 at 14:31
This doesnt help :(
– Kamil Kamil
Nov 22 at 14:36
2
2
::ng-deep, /deep/ and >>> are deprecated.
– Jai
Nov 22 at 14:28
::ng-deep, /deep/ and >>> are deprecated.
– Jai
Nov 22 at 14:28
angular.io/guide/component-styles#deprecated-deep--and-ng-deep
– Jai
Nov 22 at 14:31
angular.io/guide/component-styles#deprecated-deep--and-ng-deep
– Jai
Nov 22 at 14:31
This doesnt help :(
– Kamil Kamil
Nov 22 at 14:36
This doesnt help :(
– Kamil Kamil
Nov 22 at 14:36
add a comment |
Going from your comment about the original code this should probably work:
:host ::ng-deep .sortable-container .sortable-list ul .active {
x: value !important;
}
This assumes you're in a 'ul' but it could be ol or dl and replaced just as easily.
Don't forget theliinli.active.
– ConnorsFan
Nov 22 at 15:22
He shouldn't need it. The ul is an inserted element above the .active so it is more specific.
– rrd
Nov 22 at 15:23
add a comment |
Going from your comment about the original code this should probably work:
:host ::ng-deep .sortable-container .sortable-list ul .active {
x: value !important;
}
This assumes you're in a 'ul' but it could be ol or dl and replaced just as easily.
Don't forget theliinli.active.
– ConnorsFan
Nov 22 at 15:22
He shouldn't need it. The ul is an inserted element above the .active so it is more specific.
– rrd
Nov 22 at 15:23
add a comment |
Going from your comment about the original code this should probably work:
:host ::ng-deep .sortable-container .sortable-list ul .active {
x: value !important;
}
This assumes you're in a 'ul' but it could be ol or dl and replaced just as easily.
Going from your comment about the original code this should probably work:
:host ::ng-deep .sortable-container .sortable-list ul .active {
x: value !important;
}
This assumes you're in a 'ul' but it could be ol or dl and replaced just as easily.
answered Nov 22 at 15:20
rrd
2,83831222
2,83831222
Don't forget theliinli.active.
– ConnorsFan
Nov 22 at 15:22
He shouldn't need it. The ul is an inserted element above the .active so it is more specific.
– rrd
Nov 22 at 15:23
add a comment |
Don't forget theliinli.active.
– ConnorsFan
Nov 22 at 15:22
He shouldn't need it. The ul is an inserted element above the .active so it is more specific.
– rrd
Nov 22 at 15:23
Don't forget the
li in li.active.– ConnorsFan
Nov 22 at 15:22
Don't forget the
li in li.active.– ConnorsFan
Nov 22 at 15:22
He shouldn't need it. The ul is an inserted element above the .active so it is more specific.
– rrd
Nov 22 at 15:23
He shouldn't need it. The ul is an inserted element above the .active so it is more specific.
– rrd
Nov 22 at 15:23
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432895%2foverriding-style-that-already-has-important%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
3
You would have to make the CSS selector more specific. Can you show the HTML markup of the element and the context around it? If you could make a stackblitz showing the problem, that would be even better.
– ConnorsFan
Nov 22 at 14:19
The original style: .sortable-container .sortable-list .active I tried: body .sortable-container .sortable-list li.active
– Kamil Kamil
Nov 22 at 14:40