Skip to content

qml: ElTextArea default topPadding, hide placeholderText on input #10585

Draft
f321x wants to merge 2 commits intospesmilo:masterfrom
f321x:qml_eltextarea_padding
Draft

qml: ElTextArea default topPadding, hide placeholderText on input #10585
f321x wants to merge 2 commits intospesmilo:masterfrom
f321x:qml_eltextarea_padding

Conversation

@f321x
Copy link
Copy Markdown
Member

@f321x f321x commented Apr 17, 2026

Sets a larger (than padding) default topPadding on the ElTextArea as i noticed that all ElTextAreas look better with some more padding at the top
Followup to #10579

Also hides the placeholderText of ElTextArea as soon as the user enters something, otherwise it would conflict with the user input and look broken.

E.g. lnurlpay dialog:
before:
Screenshot_20260417_120555

after:
Screenshot_20260417_120446

f321x added 2 commits April 17, 2026 11:49
I noticed all ElTextAreas seem to look better with some topPadding,
so it makes more sense to add it as default to ElTextArea.
Followup to spesmilo#10579
When the user enters something into the ElTextArea the placeholder
text should be hidden so it doesn't conflict with the user input.
This affects e.g. the lnurl pay dialog.
@f321x f321x added the gui-qml label Apr 17, 2026
@accumulator
Copy link
Copy Markdown
Member

The current styling is basically Qt6.4 specific. I assume you run it locally with a higher Qt version? That would explain the wrong padding.
In that case, don't bother with the styling until the #10485 branch is merged

@f321x f321x marked this pull request as draft April 20, 2026 08:27
@f321x
Copy link
Copy Markdown
Member Author

f321x commented Apr 20, 2026

@accumulator Ah yes, on current the Qt 6.4 Android build this padding issue actually doesn't exist. I noticed it on Qt 6.5 (Desktop QML) and on your Qt 6.10 branch, so we should probably have a look again after #10485 is merged, or you include it in #10485.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants