Does anybody has experience using Quasar in a Liferay portlet? I would appreciate to get some information about the portlet build process.

Does Quasar offers some html ‘sanitizing functionalities’ or what is the recommended approach for using user defined HTML.
The easiest way in regard of dialog and notify plugins would be to harmonize attributes (like message, title, icon) etc.

Yes its partly user created and thus a candidate for vulnerability. Only a few attributes (similar to the dialog) could solve the problem.

Thanks, but I wanted to avoid to use html where it’s not necessary due to vulnerabilitiy.
I think this is a kind of feature request? Or is there a workaround?

Thanks. Yes I know. But I would like to use Notify plugin.

We would really appreciate if we could have apart from “message” attribute the “title” attribute for Notify API like we have in the dialog.

                    this.$q.notify({
                        title: 'Alert',
                        message: 'test',
                        textColor: "warning",
                        icon: "error"
                    });

Vice versa it would be nice to have some attributes of the dialog API like icon , textColor in Notify API.

We are using dexie as a wrapper for IndexedDB in our Quasar app.

@metalsadman Yes mousedown solves it. Thank you that is exactly what I was looking for.

@metalsadman @s-molinari Exactly. I had this once with JQuery mobile out of the box. The problem is I have to check if the state is null. But if I click/select the value is already set.
So “comparing it to current model on click” is unfortunately not possible cause the new value is already set by click. Need something before_click.