No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    [Vue warn]: Do not use built-in or reserved HTML elements as component id: Dialog

    Help
    2
    5
    4960
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ssuess
      ssuess last edited by

      I am using the dialog component, and it all seems to be working, but I have this error on any page load with a dialog:

      [Vue warn]: Do not use built-in or reserved HTML elements as component id: Dialog

      I followed the examples, my code looks like this:

      methods: {
          showDialog (rowid, index) {
            Dialog.create({
              title: 'Confirm',
              message: 'Really delete this item?',
              buttons: [
                {
                  label: 'Disagree',
                  handler: () => {
                    console.log('Disagreed...')
                    console.log('rowid:' + rowid)
                  }
                },
                {
                  label: 'Agree',
                  handler: () => {
                    this.deleteRow(rowid, index)
                  }
                }
              ]
            })
          }
      
      1 Reply Last reply Reply Quote 1
      • ssuess
        ssuess last edited by

        Anyone have a workaround for this? Am I the only one seeing this?

        1 Reply Last reply Reply Quote 0
        • C
          coxy121 last edited by

          @ssuess are you registering Dialog as a component? If so, that will cause this issue. You do not need to register it as a component, you only need to import it.

          1 Reply Last reply Reply Quote 2
          • ssuess
            ssuess last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • ssuess
              ssuess last edited by

              OH…I was also exporting it along with all the other components, I didn’t realize I didn’t need to do that as I am doing with the others. Once I removed the export, the error goes away. Thanks!

              1 Reply Last reply Reply Quote 0
              • First post
                Last post