Its common to have ‘export’ and ‘print’ table data. This is missing feature in q-table, can we have it?

I am a proud Quasar user from past 8 months, I always get the response from the community especially from @rstoenescu @s-molinari @metalsadman @Hawkeye64

@rstoenescu Thank you for your great work and quick response. I have upgraded, now everything OK.

@chyde90 Thanks for clue. I achieved this following way

columns() {
      return Object.keys(this.parsedJsonArrayOfObjectsFromCsv[0]).map(key => {
        return {
          name: key,
          label: key,
          align: "left",
          sortable: true,
          field: key
        }
      })
    }

/node_modules/@firebase/messaging/dist/index.cjs.js

You will find index.esm.js, index.cjs.js.map and index.esm.js.map also at above location.Total 4 files.

var DEFAULT_SW_PATH = ‘/service-worker.js’;
var DEFAULT_SW_SCOPE = ‘/’;

Do above two changes wherever you find DEFAULT_SW_PATH and DEFAULT_SW_SCOPE
then build again, everything will work fine.

i found my mistake that i was not using meta tag view port

<meta name=“viewport”
content=“user-scalable=no, initial-scale=1, maximum-scale=1, minimum-scale=1, width=device-width<% if (htmlWebpackPlugin.options.ctx.mode.cordova) { %>, viewport-fit=cover<% } %>”>

disabled q-item not disabling click on q-item-section, if we click on disabled q-item then also @click is getting called.

                       <q-item
                            :disable="true"
                            tag="label"
                            v-ripple
                            v-close-popup
                          >
                            <q-item-section>
                              <q-item-label  
            @click="something()"
                              >Update</q-item-label>
                            </q-item-section>
                          </q-item>

@cata-orellana
https://github.com/quasarframework/quasar/discussions/9065

useServiceWorker is deprecated

Solved it by “htmlWebpackPlugin.options.process.env.isdev”

my quasar.conf includes following

 env: ctx.dev ? { // so on dev we'll have
        isdev: true
      } : { // and on build (production):
        isdev: false
      }

I want to have a block of code in the production build only. Below is what I tried, but don’t know how to access environment?

<% if (htmlWebpackPlugin.options.environment !== 'dev') { %>
  // insert something in production only
<% } %>

@s-molinari Can we set autofocus to ‘cancel’ instead of ‘ok’ so that accidental ‘enter’ keypress event can be treated as cancelled.

@dobbel yes i am using it, but for small confirmations and prompts i have made a function with q-dialog plugin, in a mixin to reuse everywhere.

I have a situation where i need to confirm a delete operation, I faced an issue with q-dialog is that if the user accidentally presses ‘Enter’ key then is treated as ‘onOk’. i want to execute ‘onCancel’ as default for ‘enter’ key.

How can I achieve this?

@dobbel Yes, but it should prevent by default. As of now I am doing this

@click="!isdisabled && something()"

disabled q-item not disabling click on q-item-section, if we click on disabled q-item then also @click is getting called.

                       <q-item
                            :disable="true"
                            tag="label"
                            v-ripple
                            v-close-popup
                          >
                            <q-item-section>
                              <q-item-label  
            @click="something()"
                              >Update</q-item-label>
                            </q-item-section>
                          </q-item>

@metalsadman As of now, i am implementing https://github.com/hukaibaihu/vue-org-tree, but will move to q-tree in future.