-
Notifications
You must be signed in to change notification settings - Fork 6.7k
DatePicker problems with Angular 1.1.5 #760
Comments
@Swiip Thx for your report and your help getting this correct.
A PR at least for the attribute name atm would be nice! |
@bekos @Swiip even if the patch from angular/angular.js#3465 gets accepted (which I'm sure it will in this form or another) it will make it into AngularJS 1.0.8 the earliest. Which means we will still have tons of broken AngularJS versions... This is why I've decided to patch it somehow in the tooltip. Not sure if there is a way of providing a work-around in the date-picker... For the |
@Swiip Do you care to open a PR sorting these problems? I would appreciate avoiding the try blocks & about the attribute name, other than be a breaking change, I don't think we should bother more. |
Alright I'll work on a real PR and of course the try block is awful and was only a way to test quickly. For the |
These changes don't seem to be included in the official releases at https://github.com/angular-ui/bootstrap/tree/gh-pages. A custom build with the datapicker module did not work with angular 1.1.5 Is there a plan to update the official releases? |
@yong3gao1 we did a release only a week ago, we will need couple of more weeks before 0.6.0. You can clone this repository and build master branch if you need those changes earlier on. |
I did a build successfully following the instructions in README.md. Thanks. |
I updated AngularUI Bootstrap to the new version 0.0.5 in order to use ne new popup feature.
I use :
Angular UI Boostrap 0.5.0
Angular JS 1.1.5
No jQuery
I identified two problems so far (in addition to this one: #758) :
$document.unbind
inscope.$watch('isOpen'...
open
attributes. With AngularJS 1.1.5, it seems that it always be true so the button doesnt work. I only succeed to patch this by changing the attribute name.I wrote a Plunkr to illustrate : http://plnkr.co/edit/vAiD5v?p=preview
Search for
//PATCH
in bootstrap.js to find the patches. These patchs are ugly and I know this need better workarounds.If this is confirmed, I can submit a pull request with real corrections...
Matthieu
The text was updated successfully, but these errors were encountered: