Email or username:

Password:

Forgot your password?
Csepp 🌢

Why do web devs think cutting off text is a good idea? Just get rid of a few (max-)width/height properties and everything becomes readable.

This toot brought to you by #Mastodon's profile metadata always making me hover over it.

cc #webdev and #gui because this is not a rhetorical question.

8 comments
Matthew G.

@csepp Speaking as a web dev, it isn't always the developers' decision. If management wants a pixel-for-pixel match between the mockup and the implementation, there's only so much a developer can do short of quitting en masse or unionizing and staging a wildcat strike (something most techies won't consider because too many of them mistake themselves for Ayn Rand heroes).

Csepp 🌢

@fullstackthaumaturge But why does Mastodon do it? Eugen isn't beholden to any management.
I'm pretty sure there are also other open source / single person projects where I've seen this behaviour.

Matthew G.

@csepp No idea why Mastodon does it, TBH. In the case, Eugen *is* the management.

Adrian Cochrane

@csepp All I can say is CSS avoids cutting off text when unless explicitly told to. In an attitude that an ugly page is better than an illegible page...

Apparantly webdevs or their bosses dislike this default!

:garfield:‍fuchsiaaaaaaaaaaaaaaaaa

@csepp idk the reasoning is probably to keep the height consistent (or that you should only add short texts?), it does look a bit more messy with varying height rows.

But I do prefer being able to read the whole thing as well, still

Csepp 🌢

@f0x Then it should limit the length in the settings form. It feels like a designism. Pretty layout over readable content.

DELETED

@csepp In my experience tables rarely work in mobile/short width designs. Mastodon should probably change its presentation of metadata, even if that'll take more rows.

Go Up