[UserPage] Minor Fixes - Checklist

User page changes:

• show current tags in BrewItem (mimic current author listing functionality?) (#2317 / #2318)
• expand filter to include tags (#2319 / #2320)
• add URL parameters for sort by and direction ( #2315 / #2316)
• save sort by & direction to local storage; load and use when page loaded with no URL parameters present (#2326 / #2327)
• loading page with filter URLParameter does not apply filter to page (#2297)
• show current system tags (#1842 / #2330)
• rework sorting options, possibly add page count to sorting options (#1796 / #2379)
• remove autofocus from User Page (#2121 / #2305)
• add section collapsing and/or reordering ( #1797 / #2300)
• show thumbnail from metadata (if not blank) ( #2331 / #2332)
• fix centering of SortContainer when scroll bar hidden ( #2303 / #2304; follow up #2352 / #2360 & #2382)
• switch to v3 CSS (#2301 / #2302)
• smarten possessive apostrophe in usernameWithS (replace ' with ’) (#2328 / #2329)

[Gazook89]

fix centering of SortContainer when scroll bar hidden

This one can be checked off as complete.

rework sorting options, possibly add page count to sorting options

This one can also be checked off as complete, too, as far as I’m concerned. The original linked issue is closed since we decided that page count sorting wasn’t really necessary.

Unless there is anything else to add to this list immediately, I think this issue can be closed @G-Ambatte.

[Gazook89]

However, it is in line for a re-work in order to be able to add more sort categories - I’m thinking we use a :before element in the same way we’ve done the visibility icon on the headers to indicate ascending/descending order, and only have it visible on the active sorting type element.

I have a branch now that has the whole sort/filter bar reworked as a series of flex divs, rather than table. It changes the sort direction to be an icon that appears next to whichever sort option is chosen. It changes to white when hovered, as well. The filter text area moves to a second row if the screen size is dramatically reduced (for anticipation of mobile use in the far distant future). In my opinion it fits better with the UI elements, rather than with the content.