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
Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.
We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
We'll replicate the issue to ensure that the problem is as described.
We'll decide whether the behavior is an issue or if the behavior is intended.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.
Thanks, from your friendly Umbraco GitHub bot 🤖 🙂
enkelmedia
added a commit
to enkelmedia/Umbraco-CMS
that referenced
this issue
Apr 21, 2025
Which Umbraco version are you using?
v15.4.0-rc2
Bug summary
I'm trying to use the Tiptap editor (
umb-input-tiptap
) in a custom section.It works great however, there is a hard coded value for the sticky behavior here:
Umbraco-CMS/src/Umbraco.Web.UI.Client/src/packages/tiptap/components/input-tiptap/tiptap-toolbar.element.ts
Line 111 in 6455f96
Which makes it look like this in my custom section:
Specifics
No response
Steps to reproduce
...
Expected result / actual result
I'm thinking that we could make this hardcoded setting a variable so that it can be overridden if needed.
The text was updated successfully, but these errors were encountered: