Fix styling of ToS panel for consistency #2511

Open
feld wants to merge 1 commit from gitlab-mr-iid-1244 into develop
Owner
#971
Author
Owner

image

![image](/attachments/1d28fb81-0da0-4550-9251-3ea500128875)
156 KiB
Owner

I don't know if we want to do this, I don't think everyone uses the tos.html for strictly terms of service, which is why we might not want to hardcode a label for it like that. I can see plenty of people using it for generic about-information and rules more than ToS

I don't know if we want to do this, I don't think everyone uses the tos.html for strictly terms of service, which is why we might not want to hardcode a label for it like that. I can see plenty of people using it for generic about-information and rules more than ToS
Owner

for example, in my instance the panel works in the context of registration and about, but it would look weird with "Terms of Service" above it

image

for example, in my instance the panel works in the context of registration and about, but it would look weird with "Terms of Service" above it ![image](/attachments/3b28eb5d-db0c-4142-ab2b-4354371c507c)
335 KiB
Owner

base01-background

did you unearth it from 2017 or something

>`base01-background` did you unearth it from 2017 or something
Owner

panel-body does not belong within panel-heading

panel-body does not belong within panel-heading
Owner

I agree with that. I have "terms of service" written within it, but it comes after the logo, so it looks nicer like that. The duplication in @feld's screeshot (terms of service: terms of service: ....) also doesn't look right to me.

I agree with that. I have "terms of service" written within it, but it comes after the logo, so it looks nicer like that. The duplication in @feld's screeshot (terms of service: terms of service: ....) also doesn't look right to me.
Author
Owner

No, i just followed the template for other panels

No, i just followed the template for other panels
Owner

@feld ping

@feld ping
This pull request has changes conflicting with the target branch.
  • src/components/terms_of_service_panel/terms_of_service_panel.vue
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin gitlab-mr-iid-1244:gitlab-mr-iid-1244
git switch gitlab-mr-iid-1244

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch develop
git merge --no-ff gitlab-mr-iid-1244
git switch gitlab-mr-iid-1244
git rebase develop
git switch develop
git merge --ff-only gitlab-mr-iid-1244
git switch gitlab-mr-iid-1244
git rebase develop
git switch develop
git merge --no-ff gitlab-mr-iid-1244
git switch develop
git merge --squash gitlab-mr-iid-1244
git switch develop
git merge --ff-only gitlab-mr-iid-1244
git switch develop
git merge gitlab-mr-iid-1244
git push origin develop
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-fe!2511
No description provided.