Using existing styling classes found in chat, I've edited the Links module to retain an appearance/sizing that is more uniform with our Chat module interfaces
This commit fixes a text and icon alignment issue noted by @matildepark. I've simply appended a class of `lh-solid` to items in module tab bars, and removed one case of v-top.
Basically, this PR includes a collection of edits made to the headers across each of our OS1 modules.
I flattened the font sizing, fixed edge margins/padding, and fixed some button copy in the case of the Contacts app.
Prior to this commit, the commmenting component had a styling value of `mt9`, which spaced it properly away from the bottom of the post text, but rendered it with zero spacing from the bottom of the viewport in the case of no comments, and pushed right up against new comments or page navigation in an unsightly manner. This value has been edited to `mv9`, to give the comments component proper breathing room from other components.
If titles were shorter, they would still take up full-width.
I used too many "flex-autos", clearly, and this commit seems to create
the desired behaviour for both title lengths.
If we don't host a group, we can't (locally) delete it, but we do still
have a permission-hook entry we want to clean up. This does that
deletion, but still relies on the permission-hook logic to clean it up
in the local group case.
Permissions for the new group need to be exposed to the members of those
new groups. This makes the on-migrate logic poke the permission-hook for
that.
This temporary, upgrade-oriented logic depends on two assumptions:
- If the metadata-store is not running, we are still in the process of
applying the upgrade.
- If the above is true, all chats are /~host/name, all groups are
/~/~host/name, and they have a strict one-to-one relation.
Armed with those assumptions, we can deduce groups from chats and vice
versa without depending on the metadata-store, allowing us to carry on
as if it were already running.
