Drag and drop on same day does not update time in custom title formatter
See original GitHub issueDescribe the bug
Dragging an event on week view within the same day does not update the time shown in custom title formatter.
Minimal reproduction of the problem with instructions
https://stackblitz.com/edit/angular-wm4ozr
Screenshots
Versions
@angular/core
: 9.1.1angular-calendar
: 0.28.8- Browser name and version: Version 81.0.4044.122 (Official Build) (64-bit)
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Date and time in Google Sheets - Ablebits
To change it, go to File > Spreadsheet settings. You'll see a pop-up window where you can set your region under the General...
Read more >Control settings in the Format Cells dialog box - Excel
Explains that you can modify the majority of these settings in the Format Cells dialog box to change the way that your data...
Read more >Here's How You Can Create and Customize Freeform Drag ...
A correct drop target: Select this option to make the drag items return to their start point if they are not dropped on...
Read more >Create a custom cell format in Numbers on Mac - Apple Support
Type a name for your format, then click the Type pop-up menu and choose Date & Time. Define your custom format by doing...
Read more >Vue Cal - GitHub Pages
Small calendar, no time, hidden view selector & custom arrows. Extra-small, no timeline, ... Drag & drop is only available on single day...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey, thanks for reporting! I’m kind of amazed this has never come up before, I will do my best to find a way of fixing it 😄
Sounds more like a bug with angular itself rather than anything this library is doing, but if you can make a minimal repro on github that shows the problem then I can investigate further. Thanks!