-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vue.Js 3.x support #168
Comments
I want to know what is plan for vue 3.x |
For the time being you can try my fork #170 Dunno why no one is responding to the request. |
An update to VueJs 3 would be very welcomed. |
Hello guys, how we can speed up this issue. It's very important for us to upgrade froala supporting vue3. We are paying you for plugin but we can't get fresh updates. Can you pls do something???? Vue 3 was released 18 September 2020. For half year you can't support it. Not funny :( |
We're upgrading our legacy website to vue 3 and lacking vue 3 support from froala is becoming a more and more critical blocker. Ilyas Karim from support told me Vue 3 will be supported from 3.3.1 but instead it seems froala jumped from 3.2.7 to 4.0. If vue 3 wont be prioritized, please let us know so we can look at other options. |
Will there be any update on Vue 3 support in the future? |
I really need Vue JS 3 support for Froala. I am a paying customer and have been waiting patiently for the update. If you unable to support Vue 3 please let us know so I can find a different product. |
Do you have a good product recommendation |
I had recommended I tried to convert |
any updates? |
Support states that with version 4.1 Vue3 support will be fully granted. "Unfortunately, we do not support Vue 3 officially. This integration will be fully supported in version 4.1." Any infos? |
Bummer there is no Vue 3 support still, I'll have to find an alternative |
Any update? Vue3 is default now, we could really go with an update on the status of this. |
Any update on this?? |
Vue 3 - it's been 15 months since the question was asked and as everyone has said, this is now the standard and you are holding the developer community who chose Froala back not having Vue 3 compatibility. CKeditor has Vue 3 support, TinyMCE has Vue 3 support (as long back as 2020 according to their blog!), as do others. Please let everyone know when we can expect Vue 3 support. |
I've contacted Froala support a while ago and they told me that Vue 3 will be fully supported in Froala version 4.1, which they're expecting to release in Q3 this year. So it's hopefully going to happen in the next couple of months.. |
Since this issue is still going on, I'll share the information I've received. I've reached out to Froala several times about this. The first time in October 2021 they said it would be out in v4.1 which would release in December '21. That didn't happen and I reached back out in April '22. Support says that 4.1 should be out in the beginning of Q3. They did offer an alternative:
This does work to load the plugin, but I questioned it with:
To which they replied:
So basically you could do this, but don't. Why the Froala support team hasn't responded to this Github issue officially or commented on it after all this time - I don't know. I guess we just wait for them to release 4.1 while they continue to add more helpful features to core like better copy paste of links, HTML dialogs, and a broken markdown editor. |
Until this is solved by the Froala team, here is my solution, it's kind of reactive based on the Froala events. <script setup>
import { reactive } from 'vue'
import "froala-editor/css/froala_editor.pkgd.min.css"
import FroalaEditor from "froala-editor/js/froala_editor.pkgd.min.js"
let post = reactive({
content: ''
})
function initFroala() {
new FroalaEditor("#froala", {
inlineMode: false,
pastePlain: true,
paragraphy: false,
quickInsertEnabled: false,
toolbarButtons: {
// Key represents the more button from the toolbar.
moreText: {
// List of buttons used in the group.
buttons: ['clearFormatting'],
// Alignment of the group in the toolbar.
align: 'left',
// By default, 3 buttons are shown in the main toolbar. The rest of them are available when using the more button.
buttonsVisible: 1
},
moreParagraph: {
buttons: ['alignLeft', 'alignJustify', 'formatOLSimple', 'formatOL', 'formatUL'],
align: 'left',
buttonsVisible: 6
},
moreMisc: {
buttons: ['undo', 'redo', 'fullscreen', 'print', 'selectAll'],
align: 'right',
buttonsVisible: 5
}
},
// Change buttons for XS screen.
toolbarButtonsXS: [['undo', 'redo'], ['bold', 'italic', 'underline']],
placeholderText: $t('describe_thread'),
attribution: false,
key: 'enter-your-license-key-here',
disableRightClick: true,
height: 130,
fileUpload: false,
imageUpload: false,
imagePaste: false,
imagePasteProcess: false,
imageResize: false,
crossDomain: false,
events: {
'keyup': function (inputEvent) {
post.content = this.html.get()
},
'click': function (clickEvent) {
post.content = this.html.get()
},
'commands.after': function (cmd, param1, param2) {
post.content = this.html.get()
},
'paste.after': function (pasteEvent) {
post.content = this.html.get()
}
}
})
}
onMounted(() => {
initFroala()
})
</script> |
Any updates regarding this? Vue3 is a new default for at least of 8 months. I just can't understand what is taking you so long. |
The fact that we've paid for this plugin, should have considerably greater support than this. |
Our business is now in the process of moving away from Froala in every project we have. This major issue lingering so long, without proper statements and timelines, is simply unacceptable for a paid (and expensive!) product like Froala. |
This is taking way too long. Can anyone advise a good (similar) alternative? |
I'm pretty sure "Froala" is just a small subsidiary team at "Idera, Inc". Since the Froala team seems to be all but unresponsive to inquiries, has anyone by chance attempted to contact anyone at the main office to see if they have any clarity on subject? I consider vendors that provide project critical libraries as business partners, and it's difficult to make any forward leaning decisions when a non-trivial vendor just goes radio silent. |
I think I've waited quite a while Still no plans to support vue 3? |
I agree 100% that this is totally unacceptable - we are also extremely very frustrated. Our lead developer spent over a week fixing a bug with the way Froala managed multiple toolbars using iframes, submitted it to Froala back in May and as of the last update it is still not included in the latest build, so he is having to patch Froala manually every time we do an update. It’s bad enough paying major $$$ for a product, but then also paying our developers to fix bugs and not even seeing them included in the updates... horrible. |
At this point we as a community should either look to fork and resolve this ourselves or suggest some recommendations for a replacement. Vue 3 came out in 2020 and it's almost 2023, Froala either can't keep up with the demand or this isn't a priority for them. If anyone from the Froala support team can tell us what issues you're facing in this feature release perhaps we can contribute solutions. |
From Froala Customer Support:
Believe that as you will. Either way, probably not a good sign for future support, given the delay between the Vue3 release and the Froala release. It just doesn't seem like it's a priority for them to support Vue. |
I agree 100% that this is totally unacceptable - we are also extremely very frustrated.
Our lead developer spent over a week fixing a bug with the way Froala managed multiple toolbars on one screen, submitted it to Froala back in May and as of the last update it is still not included in the latest build, so he is having to patch Froala manually every time we do an update. It’s bad enough paying major $$$ for a product, but then also paying *our* developers to fix bugs and not even seeing them included in the updates, horrible.
From: Woeler ***@***.***>
Sent: September 21, 2022 7:01 AM
To: froala/vue-froala-wysiwyg ***@***.***>
Cc: jfk00ca ***@***.***>; Comment ***@***.***>
Subject: Re: [froala/vue-froala-wysiwyg] Vue.Js 3.x support (#168)
Any updates regarding this? Vue3 is a new default for at least of 8 months. I just can't understand what is taking you so long.
The fact that we've paid for this plugin, should have considerably greater support than this.
Our business is now in the process of moving away from Froala in every project we have. This major issue lingering so long, without proper statements and timelines, is simply unacceptable for a paid (and expensive!) product like Froala.
—
Reply to this email directly, view it on GitHub <#168 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABX5OH2HU7K6AFGFIWTWBDLV7LTGBANCNFSM4YG23H6Q> .
You are receiving this because you commented. <https://github.com/notifications/beacon/ABX5OH6V4AYH7VBZYWFSADTV7LTGBA5CNFSM4YG23H62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJK3YIOI.gif> Message ID: ***@***.*** ***@***.***> >
|
We have migrated to TipTap |
And we have migrated to EditorJS. |
From froala team: Support will come with 4.1 release which is "coming in next quarter". After clarification, froala team said: "mid-quarter". |
You mean version 4.1 will come out in the beginning of the third quarter of 2023? |
Meaning: May-ish. |
We are also waiting for this package to support Vue3 |
still no update? |
1 similar comment
still no update? |
We are also waiting for Vue 3 support. Any word? |
You're going to keep losing paying customers if you don't address this, or at the very least, keep us posted |
Kando UI for Vue is a good alternative if you are looking for a commercial component in Vue 3 - https://www.telerik.com/kendo-vue-ui/components/editor/ |
Any update on the Vue 3 integration release date? Are you on track for May 15 as per your earlier email communication? |
With Vue 2's EOL this year the community desperately needs Vue 3 compatibility in Froala and you originally promised it for Q4 2022. When will Vue 3 support be released? Not getting a clear answer we can depend on is very frustrating. |
We've decided to ditch Froala in favor of another editor. |
Check this out guys - https://github.com/ckeditor/ckeditor5-vue |
官网说了预计6月发布4.1,看看是否继续放鸽子 |
We wanted to buy the $3,000 perpetual license for our SaaS but we disappointedly find out they don't have a vue 3 version and also don't keep their promises. I see the 4.1 version in RC for vue 3, any news when this will be released fully? |
@crysper, what are the features that you need? Have you tried Kendo, I linked it a few replies up. |
So is the froala team still going to ignore paying customers? I'm still having to use the JS library and have to write my own bindings to force it to work. So far its been a great waste of money. |
@maxt91 yeah, we've already migrated away from it from a future release. We were already migrating lots of components over to PrimeVue anyway, and their Quill-based editor is just as feature-complete, and much more up to date, also with a MUCH smaller footprint. Oh, and it's free as in beer |
just the fact that they don't monitor the github issues and don't respond to comments, it's a red flag. I would understand if this was just a side project that some guys worked on their free time, but it's a paid product. |
@therecluse26 yeah, as soon as the license is up I will be going going away from this BS. thank you for the suggestion, will definitely be looking into it. |
Our development team has been actively working on this issue, and I'm glad to announce that we are planning to release the fix around July 8th. |
Vue3 framework upgrade is now available: https://froala.com/wysiwyg-editor/changelog/#4.1.0. |
Too late now |
where is the package for it? |
https://www.npmjs.com/package/vue-froala-wysiwyg Version 4.1.0 of the Package is for Vue 3. |
Documentation is lacking, you have inconsistent examples, references to webpack settings when Vue 3 uses Vite... |
your development team continues to ignore the needs of your customers. The new implementation still has same bugs that have been reported since 2020... |
I will echo this - last summer we spent almost 30 hours fixing a bug with iFrame alignment that caused the toolbar to go off-screen to the pop of the page, we submitted the hotfix, we have asked several times that our hotfix be deployed in builds going forward and expected it to be in this update... it is not... so even installing the updated toolbar on our side means we would have to spend 1.5 days to reimplement the hotfixes and we are seeing other bugs now as well. This is incredibly frustrating and when I wrote to Froala support about this, because as much as we want Vue 3 compatibilty we are not going to upgrade our perpetual enterprise license if these things are not fixed in the update... they told me they could not talk to us unless we renew the license or place an order and not pay, which I am not comfortable with because placing an order creates the expectation that we owe them the money, no matter the outcome. |
Y'all need vite |
Does someone have a timeline on when Froala will support Vue.Js 3.x
https://v3.vuejs.org/
The text was updated successfully, but these errors were encountered: