You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your picker is super great and light, I like it a lot!
But I found one problem when trying to use it on mobile devices for example.
First of all I had to override the width of the modal (I need it to be less than 300, let's say 260).
The thing is that you have fixed width for the picker-modal (which is 300), and this is used to determine position of the modal: https://github.com/restorando/angular-pickadate/blob/master/src/angular-pickadate.js#L49
Is there any chance that you fix this because this rule doesn't work for smaller screens or if you want to costumize the size of the modal, which makes picker modal clipped from the left side?
One of the solution would be to provide size (or width) as parameter and return it as part of the computeStyles and use it instead of fixed 300 value in order to determine position, what do you think?
The text was updated successfully, but these errors were encountered:
Hello there!
Your picker is super great and light, I like it a lot!
But I found one problem when trying to use it on mobile devices for example.
First of all I had to override the width of the modal (I need it to be less than 300, let's say 260).
The thing is that you have fixed width for the picker-modal (which is 300), and this is used to determine position of the modal:
https://github.com/restorando/angular-pickadate/blob/master/src/angular-pickadate.js#L49
Is there any chance that you fix this because this rule doesn't work for smaller screens or if you want to costumize the size of the modal, which makes picker modal clipped from the left side?
One of the solution would be to provide size (or width) as parameter and return it as part of the
computeStyles
and use it instead of fixed 300 value in order to determine position, what do you think?The text was updated successfully, but these errors were encountered: