Jake Dolan

It appears that the class `.fa-w-16` which was attached by default previously to the svgs no longer exists as of `1.3.0`. It provided a width style for the `.svg-inline--fa` class...

Browser support may vary depending on its implementation of @page (https://caniuse.com/#feat=mdn-css_at-rules_page), but you should be able to achieve this with the following in a print style for both the print...

I tackled this for my codebase recently. It required customizing the Suggestion plugin to handle this "trap" when using `allowSpaces: true`. This is necessary in part due to the regex...

For others, here is a reference to possible workaround/fix for this issue [#214](https://github.com/ueberdosis/tiptap/issues/214#issuecomment-964557956). But some version of this fix should be implemented in the suggestions package.

> There appears to be an incompatibility with how Vue 3 handles template refs. The [v-for Array Refs migration strategy](https://docs.w3cub.com/vue~3/guide/migration/array-refs) seems to work, [for my fork of this branch](https://github.com/jakedolan/bootstrap-vue/tree/vue3-compat-build), with...

For others using the Vue3 migration build, I was able to resolve the issue reported above by setting the compatConfig mode to 3 in the `SlickList`, `SlickItem` and `DragHandle` components...

This is related to what I found in issue #661 that using v-model, the updated hook for the directive in the cleave.js documentation is likely unnecessary unless you want to...

@JoaoHamerski I believe there are a lot of potential issues with this library and Vue. It is not really an issue with cleave.js but rather how it interacts with Vue...

While implementing the directive for my codebase today, it appears that the assignment to el.value is what is causing the issue that you are seeing. ```javascript update: (el) => {...