Does 0.15 pertain to quasar cli or quasar ?

@dnix Without a back button, how do we handle back navigation?

I’m a bit confused with he back button post. Could you provide us with an example of how we should implement back button into our layout when stack or a demo on how to do this? Thanks!

@terumi were you able to find a workaround? I’m having a similar issue with backbuttons. was wondering if you could share how you implemented your back button from q-tabs coming from a child route. Thanks!

@greene48 said in Transitions between pages, routes, vues:

I know this was a while ago, but in case anyone comes along, this is how I got the “subpage” sliding in from the right to work:

<template>
  <div>
    <transition :name="transitionName">
      <keep-alive>
        <router-view class="child-slide"></router-view>
      </keep-alive>
    </transition>
  </div>
</template>
<script>
export default {
  data () {
    return {
      transitionName: ''
    }
  },
  beforeRouteUpdate (to, from, next) {
    const toDepth = to.path.split('/').length
    const fromDepth = from.path.split('/').length
    this.transitionName = toDepth < fromDepth ? 'overlap-left' : 'overlap-right'
    next()
  }
}
</script>

<style>
.child-slide {
  width: 100%;
  position: absolute;
  transition: all 0.3s;
}
.overlap-left-enter, .overlap-left-enter-active {
  opacity: 0;
}
.overlap-left-enter-to {
  opacity: 1;
}
.overlap-left-leave-active {
  transform: translate(100%, 0);
}
.overlap-right-leave-active {
  z-index: -1;
  opacity: 1;
  transform: translate(-30px, 0);
}
.overlap-right-enter {
  transform: translate(100%, 0);
}
</style>

This is a bit jumpy. Was wondering if you had to a more updated version of this. Thanks!

@NT Did you finnd a solution? I’m getting the same error.

How to prevent scrolling in cordova hybrid app?

It is very annoying to be able to pull the view… is there a way to lock it in place? Thanks!

@mustotto Do you mind sharing your code base? I’m having some difficulty in integrating admob as well. Thanks!