Break down long tags on "post version" page and make the "Edits" column wider

Posted under Bugs & Features

reg panda

Post version pages are used for showing a post's, a person's or a tag's tag history.

Some tags are too long, e.g. guild_no_uketsukejou_desu_ga_zangyou_wa_iya_nanode_boss_wo_solo_toubatsu_shiyou_to_omoimasu is way too long, and it makes the edits column too narrow, I can't see my post history or the post history for that this tag's pictures. Also on post history it makes the image hidden (???)

E.g.

random picture with that copyright: https://danbooru.donmai.us/post_versions?search[post_id]=9066712
random other picture: https://danbooru.donmai.us/post_versions?search[post_id]=8281371

I believe that the tools are already there, long URLs don't cause any problems, whatever chops up the URLs could be used to chop up long-ass tags.

Additionally "Edits" is the most important column there, so all the other columns just saying "Source" or "Revert it" could be narrower.

Reply
BrokenEagle98

This isn't an issue on my browser. The overflow-wrap: anywhere CSS property on .tag-list a.search-tag links should make it so that it'll wrap the tag wherever it needs to to make it fit. Unless your browser is very old or non-standard, it should support it.

https://developer.mozilla.org/en-US/docs/Web/CSS/overflow-wrap

If you right-click on one of the tag links in the Tags column and click Inspect (on Chrome), it'll take you to that element in the dev console and show you the current CSS styles being applied to it.

Admittedly the Tag and Edits columns get excessively narrow when the browser window isn't full screen, since the table will compress to fit the available window size, but you can fix this by setting a minimum width for the table using custom CSS.

div#c-post-versions table#post-versions-table {
    min-width: 1600px;
}

This caused the post preview to be squashed down to nothing and disappear on my browser, so I also had to add the following as well.

div#c-post-versions article.post-preview {
    min-width: 180px;
}
Reply
reg panda

When the source field is a text (self upload) it still only breaks at word boundaries, so a long file name destroys the post history page. This is how it looks in Firefox, FullHD, full screen, my normal font size (170%):

Although less broken with a bit smaller font size.

Anyway I think the Tags and Edits columns are the most important on the post history page, and the other columns are less important. So if these aren't wide enough then the other columns should give them space. E.g. you could give them 30-30% table min width, I think that should work on every device and regardless how the other columns shrink or wrap (just an idea).

Reply
trapster77

reg_panda said:

When the source field is a text (self upload) it still only breaks at word boundaries, so a long file name destroys the post history page. This is how it looks in Firefox, FullHD, full screen, my normal font size (170%):

Although less broken with a bit smaller font size.

Anyway I think the Tags and Edits columns are the most important on the post history page, and the other columns are less important. So if these aren't wide enough then the other columns should give them space. E.g. you could give them 30-30% table min width, I think that should work on every device and regardless how the other columns shrink or wrap (just an idea).

if anyone needs a work around, u can just hide the columns u don't like with css https://danbooru.donmai.us/settings

#post-versions-table :where(
    .post-version-select-column,
    .version-column,
  /*.tags-column,*/
  /*.edits-column,*/
    .changes-column,
  /*.updated-column,*/
    .action-column
) { display: none; }
Reply
1