4-digit interaction numbers glitch out after full load. (seen on pleroma instance) #198

Open
opened 2022-11-08 16:56:53 +00:00 by aetios · 5 comments

It looks like 4-digit interactions glitch out on pleroma instances. I haven't been able to check on akkoma but it's worth investigating?

The 4 digits Are visible as long as the response list isnt loaded then they vanish.

It looks like 4-digit interactions glitch out on pleroma instances. I haven't been able to check on akkoma but it's worth investigating? The 4 digits Are visible as long as the response list isnt loaded then they vanish.

It all shows up properly on my instance, but the number is overflowing a bit.

It all shows up properly on my instance, but the number is overflowing a bit.
Mergan added the
Bug
label 2022-11-17 23:15:49 +00:00
Contributor

I see this as well for interactions in excess of 1k.

It looks like the responsible CSS is:

word-break: break-word styling for .Status inherited from div.

This is automatically applying flex-shrink to the likes count

if max-width of .Status .status-actions > * is set to 5em, then the likes display nominally as expected without other alterations (as in screenshot attached)

I'll see if I can figure out where this behavior is defined and submit a PR for this

I see this as well for interactions in excess of 1k. It looks like the responsible CSS is: `word-break: break-word` styling for `.Status` inherited from `div`. This is automatically applying `flex-shrink` to the likes count if `max-width` of `.Status .status-actions > *` is set to `5em`, then the likes display nominally as expected without other alterations (as in screenshot attached) I'll see if I can figure out where this behavior is defined and submit a PR for this
Contributor

So, I guess there are 2 separate issues here really, but the problem @wizard and I are experiencing should be sorted by my PR, which I've submitted for review:

AkkomaGang/pleroma-fe#233

So, I guess there are 2 separate issues here really, but the problem @wizard and I are experiencing should be sorted by my PR, which I've submitted for review: https://akkoma.dev/AkkomaGang/pleroma-fe/pulls/233
Contributor

was this fixed in #236? or did that tackle only one of the issues here

was this fixed in #236? or did that tackle only one of the issues here
Contributor

The issue @wizard(and myself) mentioned is fixed.

One of us should've split that into a separate issue for the sake of organization, but afaik ops concern wasn't.

The issue @wizard(and myself) mentioned is fixed. One of us should've split that into a separate issue for the sake of organization, but afaik ops concern wasn't.
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma-fe#198
No description provided.