Skip to content
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

Uncaught TypeError: Cannot read property 'getBoundingClientRect' of undefined #31

Open
RobSteward opened this issue Apr 18, 2021 · 3 comments

Comments

@RobSteward
Copy link

I'm using the wall to display a custom card component like so:

<div v-else>
      <v-row dense>
        <vue-masonry-wall
          :items="rules"
          :options="masonryOptions"
          :ssr="{ columns: 3 }"
        >
          <template v-slot:default="{ item }">
            <LazyRuleCard :rule="item" />
          </template>
        </vue-masonry-wall>
      </v-row>
    </div>
  • rules is a computed property passed from Vuex store that's bound to Firestore.
  • RuleCard is a component like so
<template>
  <v-card elevation="3" tile>
    <v-card-title>
        {{ rule.title }}
    </v-card-text>
     ... And so on
    <v-card-actions>
      Some card actions
    </v-card-actions>
  </v-card>
</template>

<script>
export default {
  props: ['rule'],
}
</script>
  • masonryOptions is returned from data like so
 masonryOptions: {
        width: 300,
        padding: {
          default: 12,
          1: 6,
          2: 8,
        },
      },

While the rules are displayed, I get this error in console. What am I doing wrong? Seems like this gets called for each of the 7 test rules that I have.
image
image

@RobSteward
Copy link
Author

@fuxingloh Just to check - is this something your still actively developing or should I look for other packages?

@fuxingloh
Copy link
Owner

@fuxingloh Just to check - is this something your still actively developing or should I look for other packages?

I am so sorry @RobSteward, you should look for other packages if this does not fit your use case. I am little busy with my day job now.

@RobSteward
Copy link
Author

Hi, No worries at all - I will look around. I wast just wondering if it makes sense to wait :) Good attempt though, I did like the approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants