Alex Bea
Alex Bea
We also ran into this. Passing the `--ignore-ssl-errors=yes` argument in `phantomArgs` resolved it. Obviously seems less than ideal, but works for now.
Seconding this. It is triggering an `npm audit` vulnerability warning in vue-loader, which is breaking our build test series. CC @boutell
I don't think there's anything to report right now, @potter7050. Our team continues to be focused on the next major version of ApostropheCMS. I did look at this for a...
Thanks, @potter7050. We'll review it soon.
@sunnymsf No active plans. I provided feedback on the PR #469 that could help someone move this forward. Based on my previous review, htmlparser2 might make this hard to resolve...
Do you mean you have allowedAttributes as something like `{ 'svg': ['*'] }`? With only the array that wouldn't work. Or you could use `false` to allow all attributes on...
It looks like [disabling lowercasing in the htmlparser2 options](https://github.com/fb55/htmlparser2/wiki/Parser-options#option-lowercasetags) might be a way to go when you know you're using SVGs. https://github.com/fb55/htmlparser2/issues/539#issuecomment-687579675
I looked into that when I fixed the related UI bug. I agree those errors are misleading. It would require passing the full schema into each field's `convert` function. Or...
This does seem to be a bug. I'll log it for work. I think what is happening is that the logic for finding the active style stops as soon as...
Removing the bug tag since this is only an issue with a non-recommended database.