-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read property 'tagName' of null #281
Comments
We are seeing the same error. Not clear what the root cause is.
|
We experienced the same issue. It appears that InfiniteLoader does not play nice with Vue keep-alive wrapped around the component. We noticed that Vue calls back InfiniteLoader when state changes occur on pages where InifiniteLoader is not currently rendered, which causes it to error because it thinks it can access its DOM parent, but there aren't any DOM parents when the component is not currently rendered. Here is the related issue in our project ambianic/ambianic-ui/issues/394 |
see also #254 |
anyone knows the solution? I still face the same issue with nuxt: 2.15.7 When I use keep-alive, it is breaking.. |
have same issue |
have same issue. |
I had the same problem, but already resolved :) The cause was that the component using <template>
<div>
<h1>This is Parent</h1>
<Child />
</div>
</template>
<script>
// DO NOT import HERE!
export default {
name: "Parent",
components: {
// lazy loading
Child: () => import('path/to/child.vue');
}
}
</script> <template>
<div>
<div v-for="item in items">
...
</div>
<infinite-loading @infinite="infiniteHandler"></infinite-loading>
</div>
</template>
<script>
import InfiniteLoading from "vue-infinite-loading";
export default {
name: "Child",
components: {
InfiniteLoading
},
methods: {
infiniteHandler() {...}
}
} |
Same issue with Nuxt 3 |
Version
2.4.5
Vue.js version
2.5.3
What is actually happening?
Cannot read property 'tagName' of null
Chrome Mobile 80.0.3987
browser.name. Chrome Mobile
device SM-G9500
device.family Samsung SM-G9500
The text was updated successfully, but these errors were encountered: