-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
It is not possible to resize a table's column if the editable
status of the editor changed from false
to true
(Vue 2)
#2301
Comments
editable
status of the editor changed from false
to true
(Vue 2)
editable
status of the editor changed from false
to true
(Vue 2)editable
status of the editor changed from false
to true
(Vue 2)
The same problem! |
Hey, this is a limitation of The only thing you can do right now is to re-create the editor. |
I re-created it and it is indeed working. Thank you! |
@edri Can you share your solution? |
Hi @bryanjtc, sure here is a sample of my code:
In summary, what I did is re-creating the whole editor every time my |
What’s the bug you are facing?
In my Vue 2 project, I have a TipTap editor that is disabled by default (
editable
status is set tofalse
during the initialization of the component) and that contains a resizable table.If the
editable
status of the editor changes totrue
for example after a button click, the table's columns remain not resizable, even though we can edit the content of the table.How can we reproduce the bug on our side?
Create a new table-compatible editor, which is disabled by default, then changes its
editable
status withthis.editor.setOptions({ editable: true });
. The columns remain not resizable.Here is an example: https://codesandbox.io/s/awesome-beaver-nd10k?file=/src/components/TipTap.vue
Can you provide a CodeSandbox?
https://codesandbox.io/s/awesome-beaver-nd10k?file=/src/components/TipTap.vue
What did you expect to happen?
When the editor's
editable
status changes totrue
, one should be able to resize the table's columns.Anything to add? (optional)
No response
Did you update your dependencies?
Are you sponsoring us?
The text was updated successfully, but these errors were encountered: