Sander Elias

TIL about [PostCSS](http://postcss.org/). I taught I would share it here. The reason for that is that it enables to use standard CSS (Including custom CSS properties!), and then compile it...

@LayZeeDK Well, The edge version based on chromium will land ~q1 2019. That will work there. I would love to see this feature ASAP. Runtime theming then becomes a snap!

@jpike88 By stills supporting IE11 we (the total developer community) are enabling/allowing a known insecure browser to still exists. While I do get the _leave none behind_ sentiment, I strongly...

Yes, it also works with fully custom elements. If you element mimics an input, you probably don't even need the extra attribute I created. If not, you need some extra...

@pkozlowski-opensource Even when it is not deprecated yet, it is still not the 'recommended' way to do DOM manipulation anymore. The docs still need a bit of an explainer around...

@ohois ```typescript class SomeComponent { doc = inject(DOCUMENT) ngOninit() { const document = this.doc; document.createElement('div') ... and so on } } ``` So, inject `DOCUMENT` and use that like the...

@bob-watson well, it depends 😜 seriously, if renderer is going to be deprecated, it is a different kind of discussion. I would prefer to do that, as it makes it...

@twerske, @mgechev I think it makes sense to clean up the schematics so that it doesn't add the `OnInit`. While on this, also remove the constructor. given the `inject()` function...

Ok, I reviewed this. If we are going to make a breaking change, I would say, own it, move away from SCSS, and move to CSS. There is no need...

@Harpush If we are going to get rid of `scss` we don't need a separate template file. I have some time tomorrow to dig into the actual code, after that,...