Sector Nord AG: Fixed popup description long were cut off in Customer Interface.

[jsinagowitz]

Proposed change

In the customer portal the hover popup "description long" will be cut off if it is set for the first field.

Type of change

• '1 - 🐞 bug 🐞'

Additional information

• It only happens in the customer portal.
• It only happens for the first field.

I identified the CSS setting in var/httpd/htdocs/skins/Customer/default/css/Core.Form.css:

fieldset h2 + div {
    padding-top: 13px;
    border-top: 1px solid #FFF;
    overflow: hidden;
}

I think the overflow: hidden doesn't make sense here, because it was only used for the first field in the field list so far.

Checklist

• [x] The code change is tested and works locally.(❗)
• [x] There is no commented out code in this PR.(❕)
• [ ] You improved or added new unit tests.(❕)
• [ ] Local ZnunyCodePolicy passed.(❕)
• [ ] Local UnitTests / Selenium passed.(❕)
• [x] GitHub workflow CI (UnitTests / Selenium) passed.(❗)

[dennykorsukewitz]

Hi @jsinagowitz , thanks for your report.

It only happens in the customer portal. It only happens for the first field.

I cannot reproduce this error. Can you please export a process that contains this error?

@NiklasSchmitt Can you confirm this or can you reproduce the error?

Please, keep your fork up-to-date with the upstream repository. Syncing a fork 🚀 🆙

Regards :rocket: Denny

[NiklasSchmitt]

I can not reproduce this reported behavior. I've added a very very long Lorem ipsum-string into "description long" for the first field and it's all to see into customer portal and also on agent portal.

[jsinagowitz]

I did some more research. I think you can't reproduce that because of the description in the dialog. You might need to remove that.

The "wrong" css setting is only active, if the div-tag of the first field follows the h2-tag directly.

$('fieldset h2 + div')

If you can't reproduce that eather I will send you my process. I can reproduce the bug on multiple systems.

[NiklasSchmitt]

Hi @jsinagowitz,

thank you for your additional information. I was able to reproduce the issue and I want to accept & merge your pull-request. Bur first: Please, keep your fork up-to-date with the upstream repository. See here how to sync a fork.

Best regards, Niklas Schmitt :coffee: :rocket: