@Curator .ART's custom CSS adds add overflow: scroll to .compose-form .reply-indicator__content, presumably to make it clearer that a post was truncated. Please consider changing this to "auto" instead, so that the scrollbar is only shown when actually needed. Currently it causes non-functional scrollbars to be shown on short posts, and horizontal scrollbars on all posts, even though most posts don't need them.
=> More informations about this toot | More toots from eishiya@mastodon.art
@Curator On a related note, "embedded" posts in Notifications (e.g. favourites, boosts) have display:none on paragraphs after the first, truncating silently. This CSS should "fix" that and show the usual truncation ellipsis sign, but it will make some embeds appear longer than before, so I'm not sure it's ideal.
.notification-group__embedded-status__content p {
display: unset;
}
Ideally, the web client should show a post truncation indicator instead of just hiding extra paragraphs :/
=> More informations about this toot | More toots from eishiya@mastodon.art
@eishiya Added this one too ^.^ Thank you!
=> More informations about this toot | More toots from welshpixie@mastodon.art
@welshpixie Ah, display: unset doesn't work quite as I expected to, it causes multiple paragraphs to appear on the same line (defaults to "initial" which is the same as "inline", I guess).
display: revert might be better, it just reverts the "none" but keeps the default styles. And if that doesn't work (it may work differently from custom.css than from my browser tools), there's good ol' display: block.
=> More informations about this toot | More toots from eishiya@mastodon.art
@eishiya Thanks! Just changed it. Still working on this because it's not ideal and not working as intended (if there's a line break in the post you're replying to, it skips the line break and overflows one line on top of the next)
=> More informations about this toot | More toots from welshpixie@mastodon.art
@welshpixie Aah, much better, thank you!
I don't understand what you mean about the line break thing, I don't think I've seen issues with line breaks. If you have an example post, maybe I can take a look and see if I can come up with a fix.
=> More informations about this toot | More toots from eishiya@mastodon.art
@eishiya https://glitterkitten.co.uk/@babe/113329420601269190 there you go, try replying to that one - for me it overlaps 'Love that -' over the line above
=> More informations about this toot | More toots from welshpixie@mastodon.art
@welshpixie Looks fine for me, so it might be a browser difference (I'm using Firefox) or some custom style somewhere.
This post has three paragraphs, how does it look for you? Does the third paragraph overlap this one, or is only the top paragraph that's overlapped?
Perhaps it's something to do with the first paragraph having the "h-card" class while the rest don't, and something somewhere is causing that to display weirdly.
=> More informations about this toot | More toots from eishiya@mastodon.art
@eishiya like a mess 😂 I'm on Vivaldi on Linux, don't have anything else tweaking css on the browser, just what I've got in .art's custom CSS server-side.
=> View attached media | View attached media
=> More informations about this toot | More toots from welshpixie@mastodon.art
@welshpixie I don't have Vivaldi to test with, but at least it's likely a browser-specific issue?
It looks to me like the 22px spacing "between" paragraphs is correct, but the calculated height of each paragraph is 0, so they overlap. Does Vivalvi have a way to inspect the calculated height of elements, and maybe track down the CSS causing it?
=> More informations about this toot | More toots from eishiya@mastodon.art This content has been proxied by September (3851b).Proxy Information
text/gemini