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

Bad days #18

Closed
peio72 opened this issue Oct 10, 2015 · 5 comments
Closed

Bad days #18

peio72 opened this issue Oct 10, 2015 · 5 comments
Assignees
Labels

Comments

@peio72
Copy link

peio72 commented Oct 10, 2015

I noticed there is an issue with day of the calendarbfir October and other months near the end.
There are two "25" days. You can see it on the demo page too.

@bradberger
Copy link
Collaborator

Ouch, thanks for pointing it out. Seems like it's on every day. Must have happened during the latest update. Will check it as soon as possible.

@bradberger
Copy link
Collaborator

Something definitely is not working right, now noticing that several months are not recognizing the out of month days properly either.

bradberger pushed a commit that referenced this issue Oct 10, 2015
@bradberger bradberger self-assigned this Oct 10, 2015
@bradberger
Copy link
Collaborator

Turns out it was due to improper use of one-time bindings, so this should be fixed in b711295. Website was updated, but it takes a bit for the various caches to show the changes. The updated version is 0.2.8 so make sure to use that.

@peio72
Copy link
Author

peio72 commented Oct 10, 2015

Thanx. I still can't update with latest in my app for the moment because it breaks my ajax json request and still column resizing issue. Is there a way to disable the tooltip too ?

@bradberger
Copy link
Collaborator

No the tooltip can't be disabled, but I can definitely add that as an option. Theoretically you could just load a custom template for now to do that without the tooltips.

The ajax issue is something I'm aware of, so getting that fixed is the next priority. To me it makes sense actually to change it going forward to default - perhaps even require - that the content be set via a promise (either a JS promise or $q implementation.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants