fix(Dav): make absenceform textarea not overlap

[GVodyanov]

Fix #56156

Summary

Before	After

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

[szaimen]

LGTM from screenshot but did not test

[jancborchardt]

Can’t see the autosize connection but if that automatically works on this, consider it an approval. :)

[GVodyanov]

Can’t see the autosize connection but if that automatically works on this, consider it an approval. :)

No this isn't autosize, it's just 6 rows, and after that you get a scrollbar. Speaking of autosize I would propose to add it as a feature to NcTextArea because we currently have a custom autosize implementation in contacts, and it seems we might also want one here, but I think it's better to have it directly in the component.

[hamza221]

I still get an overlap

[GVodyanov]

I still get an overlap

Should be fixed now

[hamza221]

/compile /

[hamza221]

Any DOM node within a block can be an element. Within a given block, all elements are semantically equal.

https://getbem.com/naming/

Elements should be inside blocks not the other way around

[susnux]

Maybe just rename to

• absence-long-message
• absence-long-message__input

[susnux]

good expect inverted BEM.

[jancborchardt]

Can’t see the autosize connection but if that automatically works on this, consider it an approval. :)

No this isn't autosize, it's just 6 rows, and after that you get a scrollbar. Speaking of autosize I would propose to add it as a feature to NcTextArea because we currently have a custom autosize implementation in contacts, and it seems we might also want one here, but I think it's better to have it directly in the component.

@GVodyanov Sounds good to me – we should indeed probably always have autosize on textareas, regardless of the place. Is there an issue in the components repo with the technical details already?