Skip to content

Conversation

@chrisbobbe
Copy link
Collaborator

Following a new Figma frame that specifies larger text for the first part:
https://www.figma.com/design/1JTNtYo9memgW7vV6d0ygq/Zulip-Mobile?node-id=11194-18392&m=dev

cc @alya @terpimost

👉 When there's just one thing to say (like "There are no messages here."), do we want that text to be big or small? I've chosen big, here, but that might not actually be intended in the Figma? Figma screenshot:

image

(This comes from rebasing/developing part of #1640.)

Note changed "the" to "a" on the "Direct messages" page.

Before After
image image
image image
image image
image image
image image
image image

@chrisbobbe chrisbobbe added a-design Visual and UX design maintainer review PR ready for review by Zulip maintainers product review Added by maintainers when a PR needs product review labels Oct 24, 2025
@alya
Copy link
Collaborator

alya commented Oct 24, 2025

The bigger text when we only have one sentence looks good to me.

@chrisbobbe
Copy link
Collaborator Author

Thanks for the review! Also maybe worth mentioning: the graphics in the Figma are tracked as #1551.

Copy link
Member

@rajveermalviya rajveermalviya left a comment

Choose a reason for hiding this comment

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

Thanks @chrisbobbe! LGTM, moving over to Greg's review.

@rajveermalviya rajveermalviya added integration review Added by maintainers when PR may be ready for integration and removed maintainer review PR ready for review by Zulip maintainers labels Oct 27, 2025
Copy link
Member

@gnprice gnprice left a comment

Choose a reason for hiding this comment

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

Thanks! Nits below; otherwise all looks good.

Comment on lines 234 to 236
}) : assert(
(message != null)
^ (messageWithLinkMarkup != null && onTapLink != null));
Copy link
Member

Choose a reason for hiding this comment

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

This assert seems still relevant, right?

And a similar one for the header.

Copy link
Member

Choose a reason for hiding this comment

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

Ah I see, rather it should apply only to the header.

Comment on lines 272 to 273
return null;
}
Copy link
Member

Choose a reason for hiding this comment

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

This case would be a straightforward bug at the caller. So instead of having extra logic here (including in build) to handle it, it'd be better to just use ! and end up throwing in that case.

@chrisbobbe chrisbobbe force-pushed the pr-split-placeholder-header-message branch from 51c196a to 70cc1b3 Compare October 31, 2025 21:27
@chrisbobbe
Copy link
Collaborator Author

Thanks for the review! Revision pushed.

style: _headerStyle(context),
header!);
}
return TextWithLink(
Copy link
Member

Choose a reason for hiding this comment

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

(#1946 (comment) cont'd)

Ah, and then this method's caller can be simplified by having this return non-nullable Widget 🙂

@chrisbobbe chrisbobbe force-pushed the pr-split-placeholder-header-message branch from 70cc1b3 to a3f5b81 Compare October 31, 2025 23:07
@chrisbobbe
Copy link
Collaborator Author

Indeed, thanks—revision pushed.

@gnprice gnprice force-pushed the pr-split-placeholder-header-message branch from a3f5b81 to db64354 Compare November 1, 2025 00:12
@gnprice
Copy link
Member

gnprice commented Nov 1, 2025

Thanks! Looks good; merging.

@gnprice gnprice merged commit db64354 into zulip:main Nov 1, 2025
@chrisbobbe chrisbobbe deleted the pr-split-placeholder-header-message branch November 1, 2025 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a-design Visual and UX design integration review Added by maintainers when PR may be ready for integration product review Added by maintainers when a PR needs product review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants