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

Table in Rich Text Editor with Content shows second toolbar when clicking in table #5926

Closed
TomDaria opened this issue Jul 17, 2019 · 6 comments

Comments

@TomDaria
Copy link

I am on Umbraco version 7.11.1 and I am using the Rich Text Editor (RTE).
If I have alot of text in my RTE and then add a table above the content, I see a second menu that bleeds into the cells (see attached).
I notified Umbraco and they said it is a bug and that the only workaround is to scroll up and down until the second toolbar goes away.
AddingTableToStartKitAboutUs.docx

Thanks

Tom

@TomDaria
Copy link
Author

In addition to the above, after scrolling, which moves the second toolbar down, when you start typing in any cell the toolbar jumps back up again and you can't see what you are typing in.

@nul800sebastiaan
Copy link
Member

This is a feature to help with editing tables (documented at tinymce here: https://www.tiny.cloud/docs/plugins/table/#table_toolbar)

However in the grid, it seems to be placed wrong, on top of the table instead of under it, it's supposed to look like this:

image

So hopefully a fairly simple CSS update can fix this.

As a simple hack for now, in ~\Umbraco\Views\propertyeditors\grid\grid.html I've added the following under line 1 (so under <div ng-controller="Umbraco.PropertyEditors.GridController"):

<style type="text/css">
    .mce-tinymce-inline { margin-top:32px; }
</style>

And that seems to help.

@russellshome
Copy link
Contributor

russellshome commented Apr 17, 2020

This issue also occurs in umbraco version 8.

Here is an example using v8.5.4

DisplayFile

@nul800sebastiaan
Copy link
Member

Sure, we'd love some help getting this fixed in v7 and v8!

@umbrabot
Copy link

Hi @TomDaria,

We're writing to let you know that we've added the Up For Grabs label to your issue. We feel that this issue is ideal to flag for a community member to work on it. Once flagged here, folk looking for issues to work on will know to look at yours. Of course, please feel free work on this yourself ;-). If there are any changes to this status, we'll be sure to let you know.

For more information about issues and states, have a look at this blog post

Thanks muchly, from your friendly PR team bot :-)

@emma-hq
Copy link
Contributor

emma-hq commented Mar 9, 2021

Hey there,

Wanted to drop you a message to let you know that I'm closing this issue - while it is still an issue in the latest release, it has been labelled up-for-grabs for almost a year and hasn't been picked up by contributors.

In the meantime, take a look at the workaround above as detailed by Seb if this issue is still causing you trouble.

Emma

@emma-hq emma-hq closed this as completed Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants