Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decrementing year on month view doesn't display the correct year on the navigator #6110

Closed
YounesM opened this issue Jul 20, 2018 · 2 comments
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@YounesM
Copy link
Contributor

YounesM commented Jul 20, 2018

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

Plunkr Case (Bug Reports)
Please demonstrate your case at stackblitz by using the issue template below. Issues without a test case have much less possibility to be reviewd in detail and assisted.

Current behavior
currentb
Expected behavior
ajust

https://stackblitz.com/github/primefaces/primeng-issue-template

Current behavior
If years navigator is disabled, decrementing or incrementing year on month view doesn't display the correct year on the navigator.

Expected behavior
Navigating through year should display the correct year even without the year navigator

Minimal reproduction of the problem with instructions
Add a calendar without the year navigator

What is the motivation / use case for changing the behavior?
We're using primeng in many projects and we need a working month picker.

Please tell us about your environment:

  • Angular version: 6.X
  • PrimeNG version: 6.0.1
  • Browser: all
  • Language: TypeScript

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

@cyberrranger
Copy link

cyberrranger commented Jul 20, 2018

move my problem to #6114

@YounesM
Copy link
Contributor Author

YounesM commented Jul 20, 2018

It's not the same problem, I updated the issue with the current / expected behavior

@cagataycivici cagataycivici self-assigned this Jul 23, 2018
@cagataycivici cagataycivici added the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Jul 23, 2018
@cagataycivici cagataycivici added this to the 6.0.2 milestone Jul 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

3 participants