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.

Sign up for GitHub

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

Jump to bottom

Wrong width size when events overlap #833

Closed
sebastien1200 opened this issue Dec 13, 2018 · 3 comments
Closed

Wrong width size when events overlap #833

sebastien1200 opened this issue Dec 13, 2018 · 3 comments
Labels
bug

Comments

@sebastien1200
Copy link

sebastien1200 commented Dec 13, 2018 •
edited
Loading

Describe the bug

Events does not display properly or can be space optimized.

Minimal reproduction of the problem with instructions

https://stackblitz.com/edit/angular-sykqgb

Screenshots

image

Would be nice to have A and B take the 66% width.

Versions

  • @angular/core: 6.1.10
  • angular-calendar: 0.26.4
@mattlewis92 mattlewis92 added the bug label Feb 4, 2019
@polaroi8d
Copy link

I have similar issue, there is any workaround?

image

mattlewis92 added a commit that referenced this issue Apr 21, 2019
@mattlewis92
fix(week-view): have time grid events fill available space
8571528 
Closes #833
@mattlewis92
Copy link
Owner

Fixed in 0.27.5! Thanks for reporting 😄

I have similar issue, there is any workaround?

image

Looks like a different issue (maybe styling related?). Please make a runnable stackblitz that reproduces the problem if it's still an issue. Thanks!

@polaroi8d
Copy link

Thanks @mattlewis92 i will check it

AlexGuz23 pushed a commit to AlexGuz23/calendar-utils that referenced this issue Nov 3, 2022
@jackwolfskin0302 @mattlewis92
fix: fill week view event width space
9f49216 
Closes mattlewis92/angular-calendar#833
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mattlewis92 @polaroi8d @sebastien1200