Skip to content

[stack] fix(mail): drop the page margin around emails on phones - #65296

Merged
skjnldsv merged 1 commit into
masterfrom
feature/mail-template-followups
Oct 8, 2026
Merged

skjnldsv merged 1 commit into
masterfrom
feature/mail-template-followups

Conversation

@skjnldsv

@skjnldsv skjnldsv commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

Summary

Builds on #65226. On phones the colored header now sits at the very top, without the grey margin above the card.

Notes stay before the details card for shares and after it for calendar events, see the discussion with Jan above.

Mobile before Mobile after
Calendar invitation before-invitation-light-375 after-invitation-light-375

Checklist

  • Code is properly formatted
  • Sign-off message is added to all commits
  • Tests are included
  • Screenshots before/after for front-end changes
  • Documentation has been updated or is not required
  • Backports requested where applicable
  • Labels added where applicable
  • Milestone added for target branch/version

AI (if applicable)

  • The content of this PR was partly or fully generated using AI

👾 This pull request was assisted by Claude Code, commits carry an Assisted-by trailer.

@skjnldsv skjnldsv added this to the Nextcloud 36 milestone Oct 7, 2026
@skjnldsv skjnldsv self-assigned this Oct 7, 2026
@skjnldsv
skjnldsv requested review from Altahrim, jancborchardt, leftybournes, pabzm, salmart-dev and sorbaugh and removed request for a team and sorbaugh October 7, 2026 19:16
@skjnldsv
skjnldsv added this pull request to stack #65223 October 7, 2026 19:18
@skjnldsv
skjnldsv force-pushed the feature/mail-template-followups branch 2 times, most recently from 0bacf15 to bce9b65 Compare October 8, 2026 00:56
Base automatically changed from feature/mail-footer-sender to master October 8, 2026 06:21
@skjnldsv
skjnldsv force-pushed the feature/mail-template-followups branch from bce9b65 to d92c875 Compare October 8, 2026 06:21
@skjnldsv

skjnldsv commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

@jancborchardt this is the final pr. Feel free to suggest other changes 😊

@jancborchardt jancborchardt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the bar change!

As for description relocation, it is sort of unexpected for the description to come before basic details like date and time.

Yes, for file shares it makes sense to put the "Note" above further details cause a short note is intended by the interface, but event descriptions can get quite long.

@skjnldsv

skjnldsv commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

@jancborchardt so we keep the note only above for SHares ? And for all the other after the main content ?
Good from me! :)

On narrow screens the card now fills the screen without the page
margin, so the colored header sits at the top. Tests now also pin
where notes go: before the details card for shares, after it for
calendar events and the email changed mail.

Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: John Molakvoæ <14975046+skjnldsv@users.noreply.github.com>
@skjnldsv
skjnldsv force-pushed the feature/mail-template-followups branch from d92c875 to 24ee183 Compare October 8, 2026 13:00
@skjnldsv skjnldsv changed the title [stack] fix(mail): put notes before cards and drop the mobile page margin [stack] fix(mail): drop the page margin around emails on phones Oct 8, 2026

@jancborchardt jancborchardt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, thanks! And yeah, definitely description below details is best for Calendar events.

@skjnldsv
skjnldsv merged commit 40e0db0 into master Oct 8, 2026
155 checks passed
@skjnldsv
skjnldsv deleted the feature/mail-template-followups branch October 8, 2026 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants