Skip to content
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

[V14] RTE in inline mode is unusable #16517

Open
Nuklon opened this issue May 30, 2024 · 2 comments
Open

[V14] RTE in inline mode is unusable #16517

Nuklon opened this issue May 30, 2024 · 2 comments
Labels
affected/v14 area/frontend state/needs-investigation This requires input from HQ or community to proceed state/reproduced state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@Nuklon
Copy link
Contributor

Nuklon commented May 30, 2024

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14

Bug summary

If you have RTE in "inline mode" there's nothing visible that you can edit something:

image

You have to press in the white block and hope you enter the RTE.
Which is broken on its own as the controls are half outside the view:
image

😆

Specifics

No response

Steps to reproduce

Use V14.

Expected result / actual result

No response


This item has been added to our backlog AB#41772

Copy link

Hi there @Nuklon!

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 🤖 🙂

@iOvergaard
Copy link
Contributor

Hello, and thanks for testing. I can confirm this is not in a useful state. We are configuring TinyMCE with inline:true correctly, but I honestly cannot get it to work following that. It seems Tiny's calculations of where to put the menu is all off.

I did a bit of research and discovered that Tiny doesn't support the "inline" option in their Web Component implementation either. It seems like there are issues when inside a ShadowDOM.

In fact, Tiny says that running inside a Shadow DOM is experimental at best.

We will need to discuss internally if we can support this mode and what the outlook looks like.

@iOvergaard iOvergaard added state/needs-investigation This requires input from HQ or community to proceed state/reproduced labels Jun 3, 2024
@iOvergaard iOvergaard added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affected/v14 area/frontend state/needs-investigation This requires input from HQ or community to proceed state/reproduced state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

3 participants