Transclusion : apply style to ng-content





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







3















I am facing an issue regarding how to style trasncluded content.



When reading through the documentation, it is said that there are custom selectors that can do the job. And they do ! But it is also said




The shadow-piercing descendant combinator is deprecated and support is being removed from major browsers and tools. As such we plan to drop support in Angular (for all 3 of /deep/, >>> and ::ng-deep). Until then ::ng-deep should be preferred for a broader compatibility with the tools.




This means that, because it is deprecated, those selectors should not be used.



As I am facing this issue right now, I would like to know the alternative provided to style the transcluded content.



I have asked on an old question but it doesn't seem to work for non-shadow DOM encapsulation.



Here is a stackblitz with a very minimal reproduction of the issue.










share|improve this question


















  • 1





    My understanding is that you can keep using ::ng-deep until Angular provides more info about an alternative. You can see the comment by vicb in issue #17867: "Closing this as we have no plan to remove ::ng-deep in a near future. It will be first deprecated and at this time we will provide docs about migration. Then, some time later only it will be removed."

    – ConnorsFan
    Jan 3 at 15:44




















3















I am facing an issue regarding how to style trasncluded content.



When reading through the documentation, it is said that there are custom selectors that can do the job. And they do ! But it is also said




The shadow-piercing descendant combinator is deprecated and support is being removed from major browsers and tools. As such we plan to drop support in Angular (for all 3 of /deep/, >>> and ::ng-deep). Until then ::ng-deep should be preferred for a broader compatibility with the tools.




This means that, because it is deprecated, those selectors should not be used.



As I am facing this issue right now, I would like to know the alternative provided to style the transcluded content.



I have asked on an old question but it doesn't seem to work for non-shadow DOM encapsulation.



Here is a stackblitz with a very minimal reproduction of the issue.










share|improve this question


















  • 1





    My understanding is that you can keep using ::ng-deep until Angular provides more info about an alternative. You can see the comment by vicb in issue #17867: "Closing this as we have no plan to remove ::ng-deep in a near future. It will be first deprecated and at this time we will provide docs about migration. Then, some time later only it will be removed."

    – ConnorsFan
    Jan 3 at 15:44
















3












3








3








I am facing an issue regarding how to style trasncluded content.



When reading through the documentation, it is said that there are custom selectors that can do the job. And they do ! But it is also said




The shadow-piercing descendant combinator is deprecated and support is being removed from major browsers and tools. As such we plan to drop support in Angular (for all 3 of /deep/, >>> and ::ng-deep). Until then ::ng-deep should be preferred for a broader compatibility with the tools.




This means that, because it is deprecated, those selectors should not be used.



As I am facing this issue right now, I would like to know the alternative provided to style the transcluded content.



I have asked on an old question but it doesn't seem to work for non-shadow DOM encapsulation.



Here is a stackblitz with a very minimal reproduction of the issue.










share|improve this question














I am facing an issue regarding how to style trasncluded content.



When reading through the documentation, it is said that there are custom selectors that can do the job. And they do ! But it is also said




The shadow-piercing descendant combinator is deprecated and support is being removed from major browsers and tools. As such we plan to drop support in Angular (for all 3 of /deep/, >>> and ::ng-deep). Until then ::ng-deep should be preferred for a broader compatibility with the tools.




This means that, because it is deprecated, those selectors should not be used.



As I am facing this issue right now, I would like to know the alternative provided to style the transcluded content.



I have asked on an old question but it doesn't seem to work for non-shadow DOM encapsulation.



Here is a stackblitz with a very minimal reproduction of the issue.







css angular typescript transclusion






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 3 at 12:57









trichetrichetrichetriche

30k53062




30k53062








  • 1





    My understanding is that you can keep using ::ng-deep until Angular provides more info about an alternative. You can see the comment by vicb in issue #17867: "Closing this as we have no plan to remove ::ng-deep in a near future. It will be first deprecated and at this time we will provide docs about migration. Then, some time later only it will be removed."

    – ConnorsFan
    Jan 3 at 15:44
















  • 1





    My understanding is that you can keep using ::ng-deep until Angular provides more info about an alternative. You can see the comment by vicb in issue #17867: "Closing this as we have no plan to remove ::ng-deep in a near future. It will be first deprecated and at this time we will provide docs about migration. Then, some time later only it will be removed."

    – ConnorsFan
    Jan 3 at 15:44










1




1





My understanding is that you can keep using ::ng-deep until Angular provides more info about an alternative. You can see the comment by vicb in issue #17867: "Closing this as we have no plan to remove ::ng-deep in a near future. It will be first deprecated and at this time we will provide docs about migration. Then, some time later only it will be removed."

– ConnorsFan
Jan 3 at 15:44







My understanding is that you can keep using ::ng-deep until Angular provides more info about an alternative. You can see the comment by vicb in issue #17867: "Closing this as we have no plan to remove ::ng-deep in a near future. It will be first deprecated and at this time we will provide docs about migration. Then, some time later only it will be removed."

– ConnorsFan
Jan 3 at 15:44














0






active

oldest

votes












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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54022773%2ftransclusion-apply-style-to-ng-content%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54022773%2ftransclusion-apply-style-to-ng-content%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

SQL update select statement

'app-layout' is not a known element: how to share Component with different Modules