p-header of Custom legend fails

[aamir1995]

There is no guarantee in receiving a response in GitHub Issue Tracker, If you'd like to secure our response, you may consider PrimeNG PRO Support where support is provided within 4 business hours

I'm submitting a ... (check one with "x")

[ x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Current behavior

Custom Legend for Fieldset is not working in latest 5.0.0-rc.0, If we set toggleable to True it works fine, also it seems to be work fine in previous releases
plnkr for previous release: http://plnkr.co/edit/RgG5Znx63nFC252aysat?p=preview
This issue might be introduced during this commit d325a9d

Expected behavior

The custom legend should work as expected in the latest release.

Minimal reproduction of the problem with instructions

Starter Plunker is not updated to the latest release 5.0.0, so I am posting a screenshot here.

What is the motivation/use case for changing the behavior?

Please tell us about your environment:

Windows 10
Visual studio code
NPM 5.5.1

• Angular version: 2.0.X

Angular 5

• PrimeNG version: 2.0.X

PrimeNG 5.0.0-rc.0

• Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

ALL

• Language: [all | TypeScript X.X | ES6/7 | ES5]

• Node (for AoT issues): node --version =

[rkdvep]

custom legend can be included with the 'legend' tag, instead of a header element. can you try that? View source for example: https://www.primefaces.org/primeng/#/fieldset

[aamir1995]

@rkdvep I'm talking about <p-header>Custom Legend Content</p-header> legend. I have updated the title, the previous one was a bit confusing I guess.

[sudheerj]

I can replicate the issue. It's an issue with multiple ng-content tags used in this place. Because is for static projection but not for dynamic.

angular/angular#9173