@Maxim-Van-de-Wynckel Hello! I don’t get any error with pullHook in AngularJS. I just updated the example because we slightly changed the API recently in the beta. It should be loader.state now instead of loader.getCurrentState(). This example works. Can you try it?
By the way, if you use the auto styling you don’t need to specify modifier="material" and ons-ripple, they will be added automatically on Android (ripple is added to the list item if it is tappable on iOS).
I saw that you double posted this question, but for this one, what are you needing to do? There are numerous ways to submit HTML forms and it all depends on your design environment. If you can post some sample code or provide additional details we will do what we can to help!
Currently the dialog is generally attached to the body (even though we may change that really soon), therefore it’s css is supposed to be just from the top. Generally it’s supposed to be from the top of the body. Later since we have pages which take 100% height and are scrollable everything works fine. We are doing these hacks because iOS safari has a buggy implementation of position: fixed and we’re trying not to use it.
Probably you can fix your problem by adding something like position: fixed to the style of the dialog, if you don’t care about iOS that much. Your other options are:
using ons.createAlertDialog (or just add the dialog to the body yourself)
If that’s already the case, then make sure that your other content is inside an ons-page.
using ons-modal instead - it’s supposed to move itself to the correct location. (again your content should be inside an ons-page, though if you have an infinite list maybe that’s already the case).
wait until the behaviour of alert-dialog gets changed - which will probably be relatively soon.
If none of these solutions worked for you please tell me and I will look into it once again
@ganeshspear The null means it can’t find the element attached to the DOM you are referencing. Either it doesn’t exist (you navigated to a page it is not on and are still calling the function) or you are calling the function to early in the pages creation and the element hasn’t been created yet (use ons.ready()).