-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Truncate secondary names in username and author components #19468
Conversation
Jenkins BuildsClick to see older builds (8)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
94% of end-end tests have passed
Failed tests (2)Click to expandClass TestCommunityMultipleDeviceMerged:
Expected to fail tests (1)Click to expandClass TestCommunityOneDeviceMerged:
Passed tests (45)Click to expandClass TestCommunityOneDeviceMerged:
Class TestDeepLinksOneDevice:
Class TestActivityMultipleDevicePR:
Class TestActivityMultipleDevicePRTwo:
Class TestActivityCenterContactRequestMultipleDevicePR:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestCommunityMultipleDeviceMerged:
|
8e4b4b1
to
3c5925e
Compare
@mohsen-ghafouri good catch! I've been looking into how to correct this and it seems to be complicated. A good amount of layout styles are embedded in the I've given it my best shot, and I think I've got to a good place, but more tinkering may be required to get everything tuned to the exact specs in the designs. One thought I had was to possibly separate each "element" of a component from the different layout components, and then allow Here's some updated screenshots for the current alignments: |
@status-im/mobile-qa can you review these E2E results please? 🙏 |
Hi @seanstrom I think we should ask for a design review once you believe you''ve matched the designs with the implementation. I'd say it's ok to make all the changes needed in terms of layout to get the UI correct. |
@ulisesmac Happy to do a design review, though this PR is trying to address issues with truncating secondary names. The alignments issues seem to be present in develop (unrelated to these changes I think), and I'd like to have a separate PR for re-constructing the |
…ry-name can be truncated
7343e31
to
f200637
Compare
Hey @seanstrom! Thank you for the PR. E2E failures are not PR related. |
oh ok, then it's ok. let's address it in a separate issue. thanks |
Awesome! I'll start another PR for the alignment stuff and request design review there, thank you 🙏 |
fixes #19397
Summary
quo/username
andquo/author
components to support shrinking the secondary name field when reaching the flex width of the UI.Platforms
Functional
Steps to Reproduce
The key areas of impact and steps to reproduce are described here: #19397
Before and after screenshots comparison
Before
Screen.Recording.2024-04-01.at.12.53.02.mov
After
Screen.Recording.2024-04-01.at.13.38.01.mov
status: ready