V-calendar: It is not working properly

Created on 13 Feb 2018  路  9Comments  路  Source: nathanreyes/v-calendar

Very often it closes the popup without saving the clicked date. That should never happen.
Here is jsfiddle for the example in the documentation.

bug

Most helpful comment

Please advise if the latest patch correctly addresses the issue for you.

All 9 comments

By default, the popup displays with popover-visibility set to "hover", which means it hides when a date is clicked or the mouse stops hovering the input. You can also experiment with "focus", "visible" or "hidden". You can set popover-keep-visible-on-input to true to keep the popover from hiding after a new selection is made.

I'm not sure if that addresses your problem. Any time a new date is clicked it always updates the date for my test cases. I may not be understanding your root issue here...

Same issue when popover-visibility set to "focus". On this JSFiddle this issue is happening rarely. Maybe occurs in 1/10 times when I click on the date. In my application it is happening 9/10 times. It is working always when popover-visibility is set to "visible". Event that I am using is @dayclick.

It is not that just @dayclick event is not working, than when I try to change month using arrows or try to change year, it immediately close datepicker.

@nathanreyes try the jsfiddle couple times.

Here is gif of the issue. (on the first try it does not select the date)

Like @milostimotic said, in the jsfiddle it is not working properly 1/10 times, but in my application its not working 9/10 also.

I have the same issue with popover-visibility set to focus, but it occurs rarely, mostly when I click near months.
I guess there is problem with losing focus after click

Ok. Will definitely look into it. Are you seeing any errors in the console when this happens?

Also, what browser are you experiencing this in? Does it happen in any other installed browsers?

I don't get any errors in the console.
I also happens in other browser (chrome, edge, opera, firefox).

Ok. I see where it is now.

Please advise if the latest patch correctly addresses the issue for you.

Looks like its fixed.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

garygreen picture garygreen  路  3Comments

knagyorg picture knagyorg  路  4Comments

eafomi4ev picture eafomi4ev  路  3Comments

octaviangrozman picture octaviangrozman  路  4Comments

miralize picture miralize  路  4Comments