I’ve been using Quasar since 0.13 and one of the reasons why I choose it was support for IE11 which used to be a default Browsers.
Users have a chance to us Chrome for the last two years but some users just don’t care which browser they use. They are interested only about the content. Our situation is easier thanks to Win10 on all machines - Edge and Chrome everywhere.

I think that a big game changer is a new Edge with Chromium inside and with compatibility IE11 mode which can be switched on based on the URL. We are not in this stage yet but I think it could happen by the end of this year. So, I can imagine that we don’t have to support IE11 in newly developed applications.

Answer to the question in the poll would be “down with IE11”, but keep support (security, UI fixes but not new features) for present Quasar 1.x branch at least 1/2 2021 to support current projects.

I’ve found many articles with various approaches but none of them has been working. One approach was to remove :hover from button but how to manage it for qbtn? Íll try to create custom button if it helps. Wierd is that btn works when first loaded but later it stops (i use it for navigation among question on qflashcards).

Source:
http://www.shdon.com/blog/2013/06/07/why-your-click-events-don-t-work-on-mobile-safari

Update: qbt works fine when it appears on the screen and is not part of v-if/v-else or v-show group.

Here is the link about Edge with Chromium and IE core which could be the way how to solve compatibility for big companies. I know its not always easy to talk about global changes with sys admins but the cost for supporting IE11 is also not small https://docs.microsoft.com/en-us/deployedge/edge-ie-mode

I’ve been using Quasar since 0.13 and one of the reasons why I choose it was support for IE11 which used to be a default Browsers.
Users have a chance to us Chrome for the last two years but some users just don’t care which browser they use. They are interested only about the content. Our situation is easier thanks to Win10 on all machines - Edge and Chrome everywhere.

I think that a big game changer is a new Edge with Chromium inside and with compatibility IE11 mode which can be switched on based on the URL. We are not in this stage yet but I think it could happen by the end of this year. So, I can imagine that we don’t have to support IE11 in newly developed applications.

Answer to the question in the poll would be “down with IE11”, but keep support (security, UI fixes but not new features) for present Quasar 1.x branch at least 1/2 2021 to support current projects.

Hi, I created a QTable [V1] examples on https://jsfiddle.net/mojimo/5cbzodjr/.
If I use a QTable template it does not calculate the column value as it does for simple table view. Do I have to access the calculated value in a different way then props.row.nameOfProperty? Or it is not intended behaviour and I should a put a ticket on github?

asnwer: it always returns original data #3673.

solution: @save="updateField(props.row)"

Still not perfect. How can I pass an information about a row in datatable? @Save has only old and new value. But I need to update a row in a table.

Solution is simple. If I read the documentation not only for table but also for popup edit:

 <q-popup-edit @save="updateFiled" buttons v-model="props.row.FIELD_TO_CHANGE">
   <q-field>
         <q-input v-model="props.row.FIELD_TO_CHANGE"/>
    </q-field>
</q-popup-edit>

I’d like to send a changed value from edited column to a database only if QInput field in QTable is changed. But v-model is updated with every input change - doesn’t matter if I use property to show SET and CANCEL buttons for QInput.

How should I send a changed value to database only if the field is changed (editted field is submited with enter or with SET if buttons are visible)?

 <q-popup-edit v-model="props.row.FIELD_TO_CHANGE">
      <q-field>
              <q-input v-model="props.row.FIELD_TO_CHANGE" />
       </q-field>
 </q-popup-edit>

I tried .lazy with v-model but it has no influence.

I’m struggling with the same problem whenever I publish a new versions of our apps to the Intranet but I haven’t find a way how to force Webpack change hash => change all file names to let the browser (Chrome, IE11) know that there is a new version.

this.$nextTick did the trick to solve IE11 issue.

<q-tooltip v-show="isRendered" :offset="[0,15]">{{course.ZKRATKA}} - ID: {{course.ID}}</q-tooltip>

mounted () {
      this.$nextTick(function () {
        this.isRendered = true
      })
    }

Recommended source with cheatsheets is also great and not only for Vue Js.

Thanks a lot for your advice!