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
[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
Plunkr Case (Bug Reports)
#Irrelevant
Current behavior
The documentation of confirm dialog component has some errors in default values and types.
Expected behavior
The correct default values and types in documentation.
What is the motivation / use case for changing the behavior?
Just to contribute
Please tell us about your environment:
Notepad
Angular version: 2.0.X
Irrelevant
PrimeNG version: 2.0.X
Lastest
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 ]
Irrelevant
I'm submitting a ... (check one with "x")
Plunkr Case (Bug Reports)
#Irrelevant
Current behavior
The documentation of confirm dialog component has some errors in default values and types.
Expected behavior
The correct default values and types in documentation.
Minimal reproduction of the problem with instructions
You can see the incorrect values in showcase http://www.primefaces.org/primeng/#/confirmdialog
What is the motivation / use case for changing the behavior?
Just to contribute
Please tell us about your environment:
Notepad
Angular version: 2.0.X
Irrelevant
PrimeNG version: 2.0.X
Lastest
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 ]
Irrelevant
Language: [all | TypeScript X.X | ES6/7 | ES5]
Irrelevant
Node (for AoT issues):
node --version
=Irrelevant
PR: #1964
The text was updated successfully, but these errors were encountered: