Currently the read tags get obscured by the hover menu, the hover menu should be moved inward more. It currently follows Discord's alignment, but this is not Discord and we have features from other services that need to be accommodated.
Expected Behavior: Move the hoverbar an inch or two to the left so read tags can be observed or clicked.
Currently the read tags get obscured by the hover menu, the hover menu should be moved inward more. It currently follows Discord's alignment, but this is not Discord and we have features from other services that need to be accommodated.
Expected Behavior: Move the hoverbar an inch or two to the left so read tags can be observed or clicked.
The toolbar now clears the read markers rather than sitting on top of them. The offset is the marker cluster's widest form — three overlapped 14px faces and a +N — so it moves exactly far enough and no further, and only on rows that have readers: an IRC channel has no read receipts and should not have its toolbar shoved inwards for something that is not there.
You were right that following Discord's alignment was the mistake. Discord puts it hard against the edge because Discord has nothing else there.
Also removed the old mitigation, which was to fade the markers to a quarter opacity on hover — a way of saying the toolbar wins rather than a way of both fitting.
Done in moho [fd35eb0](https://git.salastil.com/Salastil/moho/commit/fd35eb0).
The toolbar now clears the read markers rather than sitting on top of them. The offset is the marker cluster's widest form — three overlapped 14px faces and a `+N` — so it moves exactly far enough and no further, and only on rows that have readers: an IRC channel has no read receipts and should not have its toolbar shoved inwards for something that is not there.
You were right that following Discord's alignment was the mistake. Discord puts it hard against the edge because Discord has nothing else there.
Also removed the old mitigation, which was to fade the markers to a quarter opacity on hover — a way of saying the toolbar wins rather than a way of both fitting.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently the read tags get obscured by the hover menu, the hover menu should be moved inward more. It currently follows Discord's alignment, but this is not Discord and we have features from other services that need to be accommodated.
Expected Behavior: Move the hoverbar an inch or two to the left so read tags can be observed or clicked.
Done in moho fd35eb0.
The toolbar now clears the read markers rather than sitting on top of them. The offset is the marker cluster's widest form — three overlapped 14px faces and a
+N— so it moves exactly far enough and no further, and only on rows that have readers: an IRC channel has no read receipts and should not have its toolbar shoved inwards for something that is not there.You were right that following Discord's alignment was the mistake. Discord puts it hard against the edge because Discord has nothing else there.
Also removed the old mitigation, which was to fade the markers to a quarter opacity on hover — a way of saying the toolbar wins rather than a way of both fitting.