You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When using tiptap with vue-3 and scoped styles, scoped styles are not displayed on rendered nodes if there is any data (e.g. ref) or event binding attached.
Steps to reproduce the bug
Steps to reproduce the behavior:
Expected behavior
The scopedId's should be applied to every element of the component resulting in the first image.
Screenshot, video, or GIF
Should be:
Is state:
Environment?
operating system: Windows 10
browser: firefox
mobile/desktop: desktop
tiptap version: 2.0.0-beta.110
tiptap/vue-3: 2.0.0-beta.61
Additional context
After some debugging it appears that the original scopeId is hidden after extending the original component inside VueNodeViewRenderer.ts@VueNodeView which results in it not being set by setCurrentRenderingInstance https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/componentRenderContext.ts. The reason that the other scopeId's on non bound elements are still applied is due to precomputed values, which are precomputed inside the original component.
I haven't been able to find a fix on my own so far.
The text was updated successfully, but these errors were encountered:
Description
When using tiptap with vue-3 and scoped styles, scoped styles are not displayed on rendered nodes if there is any data (e.g. ref) or event binding attached.
Steps to reproduce the bug
Steps to reproduce the behavior:
Expected behavior
The scopedId's should be applied to every element of the component resulting in the first image.
Screenshot, video, or GIF
Should be:
Is state:
Environment?
Additional context
After some debugging it appears that the original scopeId is hidden after extending the original component inside VueNodeViewRenderer.ts@VueNodeView which results in it not being set by setCurrentRenderingInstance https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/componentRenderContext.ts. The reason that the other scopeId's on non bound elements are still applied is due to precomputed values, which are precomputed inside the original component.
I haven't been able to find a fix on my own so far.
The text was updated successfully, but these errors were encountered: