You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The display of the custom labeling (templating) of the ProgressBar does not work as expected.
In the StackBlitz preview from the documentation it works, unfortunately I cannot reproduce this functionality.
Environment
Windows 10, Visual Studio Code, Chrome
Reproducer
No response
Angular version
18.1.0
PrimeNG version
17.18.6
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.16.0
Browser(s)
Chrome, Edge
Steps to reproduce the behavior
Create Angular project with ng new pbar-test --no-standalone
Choose SCSS and disable pre rendering
Install primeng with npm install primeng
Add ProgressBarModule to AppModule
Copy and paste ProgressBar-Template of prime ng docs:
So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation and try the latest PrimeNG version(v19). If there is no improvement on this, can you open a new issue so we can include it in our roadmap?
Thanks a lot for your understanding!
Best Regards,
Describe the bug
The display of the custom labeling (templating) of the ProgressBar does not work as expected.
In the StackBlitz preview from the documentation it works, unfortunately I cannot reproduce this functionality.
Environment
Windows 10, Visual Studio Code, Chrome
Reproducer
No response
Angular version
18.1.0
PrimeNG version
17.18.6
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.16.0
Browser(s)
Chrome, Edge
Steps to reproduce the behavior
ng new pbar-test --no-standalone
npm install primeng
It shows 50% inside the progress bar.
Expected behavior
It is expected that it will say 50/100.
The text was updated successfully, but these errors were encountered: