Default encapsulation doesn't work after init in boostrapModule
See original GitHub issueWhich @angular/* package(s) are the source of the bug?
core
Is this a regression?
No
Description
const bootstrap = () =>
platformBrowserDynamic().bootstrapModule(AppBrowserModule, {
defaultEncapsulation: ViewEncapsulation.ShadowDom
});
find example-avatar
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
I expect behavior to change encapsulation!
Please provide the environment you discovered this bug in (run ng version
)
Angular 9
Node.js 16
npm 6
Anything else?
ps: other question why is there no property defaultChangeDetection in CompilerOptions?
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Launching your app with a root module - Angular
The default application created by the Angular CLI only has one component, AppComponent , so it is in both the declarations and the...
Read more >Storing injector instance for use in components - Stack Overflow
Now doing the same in bootstrapModule().then() doesn't work because components seems to start to execute before the promise. Is there a way to ......
Read more >48 answers on StackOverflow to the most popular Angular ...
Angular provides lifecycle hook ngOnInit by default. Why should ngOnInit be used, if we already have a constructor ?
Read more >Chapter 6. Implementing component communications
Think of an Angular component as a black box with outlets. ... all input variables are initialized with default values, ... bootstrapModule(AppModule);.
Read more >Router Guards • Angular - codecraft.tv
With guards we can add checks to restrict access to a user to certain pages on our site. Depending on the type of...
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
That sounds like a feature request unrelated to this issue report. We don’t have any intentions to widen the JIT configuration options, quite the opposite: these options don’t work in AOT compilations (and never will) and we tend to prefer self-contained components.
@JoostK
I don't understand what you mean by defaultChangeDetection.
I mean