fix(QIcon): Add check for lowercase 'm' for valid start of svg path

[hawkeye64]

Some icon sets work perfectly well with lowercase 'm' and when adding M0 0z causes a black dot in upper-left of the icon. In this case, the regex needs to be /^M|m/

[hawkeye64]

I have tested this with the change in dev and it works perfectly fine. None of the other icon sets were disturbed.

[rstoenescu]

/^M|m/ fails when the string contains "m" anywhere inside of it.
Correct is /^[Mm]/ --> pushed commit to fix it.

[rstoenescu]

Also, this broke all mdi icons...
Fixed to /^[Mm] ?\d/

[hawkeye64]

I forgot, this also needs to be done for v1

[hawkeye64]

In v1, this seems to cause an issue for mdi... icons. Working on a fix.

[hawkeye64]

#11583

I am going to re-review this update (into v2) to make sure there is no conflict with mdi

[rstoenescu]

Fixed it already. And shipped it in latest Quasar

[onurkose]

Hi, I have problems rendering simAmazon on Quasar v.2.3.4

const mRE = /^[Mm] ?\d/ is not detecting simAmazon's beginning M.045

I believe it should be like this to support dots right after first character: /^[Mm][ ?\d|.]/

[pdanpdan]

Of course it was a catch somewhere.
I suppose it could also be +- - I just hope e is not

[hawkeye64]

Yes, this didn't work out the way intended. Before Quasar update:

Quasar v2.3.4 update:

The icons are being interpreted as material-icons

I'll dig into this.

[hawkeye64]

#11584

[hawkeye64]

Fix is also added into v1: #11583

[haasz]

Hi,
When will there be a new release with the fix, that is, when will version 2.3.5 (or 2.4.0) be released?

[rstoenescu]

@haasz It's coming this week. Next Quasar version is a big one, which is why it's taking a bit more time to be released.

[haasz]

@rstoenescu Thanks for the reply.