I’m pretty sure this stems from a recent update — it used to be contained.
The Received email log is nicely contained because it has fewer columns:
The Sent and Rejected logs overflow:
I’m pretty sure this stems from a recent update — it used to be contained.
The Received email log is nicely contained because it has fewer columns:
The Sent and Rejected logs overflow:
Im not sure I see the problem, are you saying they are overflowing the page? They seem to have a horizontal scrollbar, so I think not?
Perhaps ‘overflow’ is not the best way to describe the issue. Previously there was no need for a horizontal scroll bar - everything used fit in the container.
There has been a recent change indeed
So this is the intended design. The alternative is a more squashed look.
Eventually, at a small enough width, the table is going to overflow horizontally and you need scroll. I guess you are reaching that point a bit quicker on your viewport now.
I see, thanks. I still prefer a squashed look over horizontal scrolling. Perhaps smaller text and less white space?
I noticed the change too – it’s especially awkward in Sent. Things seemed fine before the update.
The width of the Default/Foundation theme, at least, is constrained by design – not by viewport. I can only expose more of the table with CSS mods:
:root {
--d-max-width: 1310px;
}
It would be neat if we could enable/disable columns, but short of that:
I posted this earlier over at Admin pages should be full width:
It seems a bit too easy, but I’m having good luck with this CSS tweak:
// expand admin pages to full width .admin-interface { --d-max-width: 100%; }It doesn’t affect internal dialogs of course, and on some admin pages it’s overkill, but gosh it makes logs nicer.
I’d been meaning to report this. Happy to see others are noticing the same issue.
IMO, losing the ability to glance at the Post & SMTP details column without side-scrolling is really annoying.
I’m wondering if the Reply Key could be squished (perhaps a middle segment of it dropped). It’s a 32 char hex string. The first eight and last eight chars would be enough uniqueness to identify the record and save a lot of space
59e6a6c3ca31f7405d7c234d6d73bf53
vs
59e6a6c3…6d73bf53
Maybe some nice feature like hover displaying the entire 32 chars and Ctrl-V (copy) grabbing the whole thing.