chintankavathia
chintankavathia
@devversion Any specific timeline when we get this fixed?
@timowolf Could you please review this?
Not needed anymore
> I might miss something from a quick glance. What would happen if someone wants to explicitly avoid the ng-content default and project zero nodes? Should `null` be used for...
> It does sound like this would be a breaking change though? You are right 💯 . so now the question is should we do this as breaking change or...
In what situations might a user want to skip the projection and avoid falling back to the default value? Generally, when directly using a component in a template, falling back...
> `projectableNodes` should work, see https://github.com/angular/angular/blob/main/packages/core/test/acceptance/content_spec.ts#L1649 @crisbeto It works in the test because it is only testing with single projectableNode. Consider a scenario where you want to give like this....
> I guess the better solution here would, to just use the same scrollbar for body and header. Then we can get rid of all that stuff We have vertical...
May be you want to try https://siemens.github.io/ngx-datatable/#horz-vert-scrolling 😉
Hey @crisbeto, is there a plan to support this use case? If not, we should mention this limitation in our @angular/elements docs somewhere. Thank you!