Hi maybe it helps. This is working for me quite good with the animate.css library.

      <transition
              name="transitions"
              enter-active-class="animated slideInUp"
              leave-active-class="animated fadeOut"
              mode="out-in"
      >
      <router-view class="layout-view"></router-view>
      </transition>

@rstoenescu sure no problem! I was wondering if someone encountered this error but it seems that no. I will investigate too. If I come up with something I let you know.

@s-molinari that is what I actually did, I have already seen that thread. But thanks for helping

You cannot modify the slot, you have to wrap it with another element, a div for example.

Now I am actually traveling. So as soon as I get good internet I’ll push my changes to the fork and ask for a PR. I will link it here.

Thanks again!

Pull Request done: https://github.com/quasarframework/quasar/pull/413

Hi maybe the matter is crosswalk. As it was recently know crosswalk it will no longer get support. If it’s that the issue maybe you should try uninstalling it, your bundle size will be reduced a lot.

Don’t know if this is what you are talking about. But if you drag the sidebar on desktop mode, this one overlaps the content and after releasing it the content adjusts it self in a awkward way to match layout. This does not happen if you click on the hamburger button.

Ex.:

Hi maybe the matter is crosswalk. As it was recently know crosswalk it will no longer get support. If it’s that the issue maybe you should try uninstalling it, your bundle size will be reduced a lot.

“(100% ready) Material Ripples”

Do you refer to the ripple animation?

Inside Cordova dir if you have already wrapped Quasar app with Cordova just run: Cordova build [platform]. Platform stands for ios/android

Pull Request done: https://github.com/quasarframework/quasar/pull/413

@s-molinari that is what I actually did, I have already seen that thread. But thanks for helping

You cannot modify the slot, you have to wrap it with another element, a div for example.

Now I am actually traveling. So as soon as I get good internet I’ll push my changes to the fork and ask for a PR. I will link it here.

Thanks again!

Hmmm I checked the date time component and the popover also has this issue. Losses anchor and gets positioned to top and not to the triggering element. I solved nesting the <slot> in the popover component with a div of max-height 50vh (it seems that it is not possible to bind styles to slots yet in vue). I will PR now so you can check it out. I think it’s a quick easy fix.

Sure no problem. I will make a PR to give all popovers a standard height so there is no conflict with any popover triggered. As soon I can I will make the request.

@rstoenescu I found the issue. The problem was that I was giving the “.list” class a height of 100vh. Because of this, don’t know really why, de popover loses it’s anchor.
This also happens in your popover example with the “assignment” button.

In your example the the list displays a 20 elements and with a max-height of 500px. If you shorten the list to, for example, 2 elements the popover won’t lose the anchor. Also if you change the max-height to something like 200px you can preserve the amount of elements in the list without loosing the anchor for the popover.

Conclusion, big heights breaks the anchor position for the popover. Temporary fix? I think that setting the max-amount displayed to 3 or 4 elements in the autocomplete or giving a max-height of 200/300px to the list container inside the popover in the autocomplete component could solve it.

Okey. I will do that. Now I didn’t found what it’s cussing it yet. But there are props delcleared in the auto complete component over the popover that do not belong to the popover component itself. I will fork and clone the repo and try it out.