Topics created by tbrcrl

@tbrcrl I think you can use ons.ready for everything. It should be almost the same as $(document).ready, if not the same.

@tbrcrl Well, they are styled by CSS. My preferred way to do this is to not replace the onsen-css-components, but just add what is needed in my own CSS file before it. Also, with the theme roller, if you click on the component it will show you just what is for that component. I eliminate anything I didn’t change and this has helped significantly throughout the updates.

@munsterlander @Fran-Diox I tryed the disable-auto-styling attribute and it works fine. I agree with @munsterlander about the need to update the documentation both in https://onsen.io/v2/docs/js/ons-ripple.html and https://tutorial.onsen.io/?framework=vanilla&category=Reference&module=ripple as in both cases, on page 3/3, it is stated that "for the element the support the ripple attribute, <ons-button> <ons-fab> <ons-speed-dial-item> <ons-list-item> adding a ripple effect is very simple <ons-button ripple> Tap me! </ons-button> I suggest to add what @Fran-Diox stated i.e. “Autostyling is automatically adding ripple effect to ons-fab and ons-button for Material Design”. Thanks again for the promt answer.

@tbrcrl As the others mentioned we aren’t sure if and when a feature like this may be added to the core. In the meantime feel free to use something like this. It’s just a basic demo showing some minor tweaks in classes and styles. It may depend on your app, but I think something like it should be sufficient for most basic cases. Looking at the behaviour of skype and youtube android apps it seems there are minor differences. In both you can actually drag the toolbar between being shown or not and when you stop dragging it chooses its preferred state. To implement the dragging part you would need to listen for start, movement and end of the drag. So in order to keep things relatively simple I omitted that logic and only made 2 states with a small transition between them. As for hiding the tabbar menu - in both apps the tabs would always persist regardless of the circumstances, so maybe you shouldn’t try to hide yours. If you still want to the logic would be similar to what is shown in the upper example. Also the example shows js logic on the scroll event - if you just want a simple solution without any code in which the toolbar scrolls as if it’s part of the content then you can just add the attribute inline to it and you’re good to go.