mentionSuggestions - popping behind some fields instead of infront

Widgets
1

in <PROJECT_NAME> - when editing a field

if you put in a text area $/kst (or anything else) you are supposed to get a suggestion dropdown

this dropdown is a popup that is supposed to be on top of other components.
but some of the components are on top of it.

I tried adding z-index to .mentionsSuggestions
I tried many other things that might help but nothing worked

I would have solved the issue by myself if I had access to the code and I could force the popup to stay, but every time I inspect it it goes away so its impossible to debug.

see <PROJECT_NAME>-880 <INTERNAL_LINK>

51
51892×624 39.7 KB
03
031464×1524 174 KB

2

Hi Itzik,

the screenshot shows the rich-text editor from the ERU webtools code 5.2.0-rc.1. In this version, we still use our own project-specific rich-text editor solution. The update to the latest A12 Version 2018.5 introduced some issues, e.g. mentionSuggestions popup not usable.

For the next release of ERU webtools (02/2019), we use the rich-text editor widget from the A12 widget library (<INTERNAL_LINK>). Would it be fine for your to wait for the next release? For me, it does not make sense to provide a patch: effort would be too high, and this code gets replaced anyway by the a12 widget.

3

so if I understand correctly:

  1. its a known issue
  2. there is no official release with the solution yet
    please confirm that.

and a question:
there is no small css only solution that I can copy paste to our styles?

if its fine to wait or not I have to ask the project leader, I will consult with her.

4

Unfortunately, I also struggled with a quick css-only solution. Maybe someone of the Widgets/Plasma-Team can help out…

  1. Yes. :slight_smile:
  2. No, and the official release will happen in 02/19. But I can offer a release candidate, if you would like to test the next version. Just get back to me, when you have talked to your project lead.
5

According to Ferdinand its not a major issue and we can wait for the release.

6

Hi,

we havn’t only an overlay problem with the richtext editor in the webtools editor.
overlayProblem
Will your solution only effect the webtools editor or base richtext-editor?

Best regards
Nora

7

Hi @itzhak-broad-chasm,

Currently, the showcase of rich-text Editor [here]<INTERNAL_LINK> is just stand-alone rich-text Editor so that maybe there are many issues we don’t even know.
And I don’t think the next major release can fix this bug although we already had variety bugs fix for rich-text Editor.

It would be nice if you can show me your HTML structure (where the rich-text Editor is used) so that I can investigate the issue :slight_smile:

Cheers,
Nhung.

8

Hi @ntcnguyen_inactive,

if you want, we can make an appointment, where I can show you the parts of our code/HTML structure, you want/need to see.

Cheers,
Nora

9

My solution does only effect specific problems with the webtools editor (like the one from Itzik). All problems with the base rich text editor then also might be in the next webtools release :wink:

10

@anon10130690,

Actually, maybe just an image (screenshot…) of the HMTL structure is enough.
But if you have time, an appointment will be best :slight_smile:

11

hi @ntcnguyen_inactive
If you look back a little in the comments, Jan said that it will be fixed in the next release,
so which one is it?

to reproduce it

  1. go to this link: <INTERNAL_LINK>
  2. login with admin admin
  3. press Vordrucke Tab
  4. open korperschaftsteuer → kst1
  5. press the top right lock button
  6. browse the tree and edit a field using the right most button (to open Webtools field editor)

now you can write in one of the text areas $/kst and pause to get the menu