Skip to content
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

added ens name inside a div #254

Closed
wants to merge 5 commits into from

Conversation

Sadaf-A
Copy link

@Sadaf-A Sadaf-A commented Jul 5, 2024

Resolves #237
putting the ens name inside of a div utilises the existing css to handle overflowing names

@Sadaf-A Sadaf-A requested a review from Keyrxng as a code owner July 5, 2024 19:26
@Keyrxng
Copy link
Contributor

Keyrxng commented Jul 5, 2024

@Sadaf-A can you include at least one screenshot showing that it works please? Try to do this with any UI change PRs if you can.

As far as I can tell this does not resolve the issue. This name should be cut to size and have an ellipsis or elegantly wrap without breaking the table.

image
image

@Sadaf-A
Copy link
Author

Sadaf-A commented Jul 5, 2024

@Sadaf-A can you include at least one screenshot showing that it works please? Try to do this with any UI change PRs if you can.

As far as I can tell this does not resolve the issue. This name should be cut to size and have an ellipsis or elegantly wrap without breaking the table.

image image

Screenshot 2024-07-06 at 1 40 22 AM

@ubiquity-os-deployer
Copy link

ubiquity-os-deployer bot commented Jul 5, 2024

@Sadaf-A
Copy link
Author

Sadaf-A commented Jul 5, 2024

@Sadaf-A can you include at least one screenshot showing that it works please? Try to do this with any UI change PRs if you can.

As far as I can tell this does not resolve the issue. This name should be cut to size and have an ellipsis or elegantly wrap without breaking the table.

image image

Hey, I made some more changes here are the final results.

Screenshot 2024-07-10 at 10 33 01 PM Screenshot 2024-07-10 at 10 33 11 PM Screenshot 2024-07-10 at 10 33 27 PM

@@ -85,6 +85,8 @@ table td div {
word-break: break-all;
overflow: hidden;
text-overflow: ellipsis;
white-space: nowrap;
max-width: 200px;
Copy link
Contributor

Choose a reason for hiding this comment

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

Why 200px, is this the most optimal width given the available space across mobile and desktop?

Copy link
Author

Choose a reason for hiding this comment

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

I changed it to 240px here is how it will look on an iPhone SE

Screenshot 2024-07-06 at 2 33 55 AM

I think increasing it further may cause issues

Copy link
Contributor

Choose a reason for hiding this comment

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

I do too but I also think this approach isn't very responsive and could be improved to cater for other viewports. While it may also resolve the other overlap I mentioned, it will likely make it harder to effectively size both.

You have the right idea mate it's just the getting the execution right now.

P.S I appreciate the images as will other reviewers but one after each edit is not required, you can keep one or two main images/videos in the first comment up to date when you are satisfied with your changes. The odd image throughout the PR is okay but it makes it easier for other reviewers to quickly grasp where you at with things if it's up the top. Thanks @Sadaf-A

@Keyrxng
Copy link
Contributor

Keyrxng commented Jul 5, 2024

@Sadaf-A you have also resolved the additional overlapping issue contained within the #additionalDetails component with this approach which is a bonus well done. I'd suggest trying to make better use of the available space across mobile/desktop.

@Keyrxng
Copy link
Contributor

Keyrxng commented Jul 5, 2024

@Sadaf-A could you also try to use conventional commits cheatsheet, it's part of CI and will hold back PRs if CI cannot complete without issues (except under special circumstances) action repo

@Sadaf-A
Copy link
Author

Sadaf-A commented Jul 9, 2024

@Sadaf-A could you also try to use conventional commits cheatsheet, it's part of CI and will hold back PRs if CI cannot complete without issues (except under special circumstances) action repo

Hey, please provide your inputs now

@Keyrxng
Copy link
Contributor

Keyrxng commented Jul 10, 2024

The code works and looks fine.

How those changes look aesthetically will need additional confirmation whether they are suitable enough to be merged.


Personally I think the space could be better used, what do you think @rndquu?

Three viewports showing how changes affect the UI (ens name is pasted 3 times)

triple
triple-add-details

@Sadaf-A
Copy link
Author

Sadaf-A commented Jul 10, 2024

@Sadaf-A can you include at least one screenshot showing that it works please? Try to do this with any UI change PRs if you can.
As far as I can tell this does not resolve the issue. This name should be cut to size and have an ellipsis or elegantly wrap without breaking the table.
image image

Hey, I made some more changes here are the final results.

Screenshot 2024-07-10 at 10 33 01 PM Screenshot 2024-07-10 at 10 33 11 PM Screenshot 2024-07-10 at 10 33 27 PM

updated view here

@Keyrxng
Copy link
Contributor

Keyrxng commented Jul 10, 2024

Better use of the space for sure, only one or two viewports does it still happen (Galaxy S8+ #additionalDetails.from)

It could be tweaked and tweaked but this might be as good as you'll get things unless you handle each of the two areas separately.

Because by fixing the #additionalDetails.from on those viewports you are sacrificing space on others, however, the spec is to ensure that no overflow occurs so that should be the priority.

I'd suggest to shave off just enough that no overflow happens on any viewport or to handle them separately, thanks @Sadaf-A

@Sadaf-A
Copy link
Author

Sadaf-A commented Jul 13, 2024

Better use of the space for sure, only one or two viewports does it still happen (Galaxy S8+ #additionalDetails.from)

It could be tweaked and tweaked but this might be as good as you'll get things unless you handle each of the two areas separately.

Because by fixing the #additionalDetails.from on those viewports you are sacrificing space on others, however, the spec is to ensure that no overflow occurs so that should be the priority.

I'd suggest to shave off just enough that no overflow happens on any viewport or to handle them separately, thanks @Sadaf-A

could you please elaborate like what is the PR missing?

@Keyrxng
Copy link
Contributor

Keyrxng commented Jul 13, 2024

Better use of the space for sure, only one or two viewports does it still happen (Galaxy S8+ #additionalDetails.from)

I'd suggest to shave off just enough that no overflow happens on any viewport or to handle them separately, thanks @Sadaf-A

Your solution affects another part of the UI which means you now need to ensure that both parts are error free if you intend on using this solution. See the first quote above for where the error still exists and the second quote for what I suggest to do.

@rndquu rndquu self-requested a review July 17, 2024 13:30
Copy link
Member

@rndquu rndquu left a comment

Choose a reason for hiding this comment

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

  1. The issue with this approach is that if we change the container width (for example make it bigger) then there will be an empty space where ENS name could be rendered:
Screenshot 2024-07-17 at 17 00 13

Can't we use flexbox without manually setting max-width in the css files?

  1. It makes sense to be more specific in CSS selectors in order not to break anything. So if you wrap ENS name in a div then wrap it in smth like <div class="ens-name"> which can be later utilized in css files like div.ens-name. This way we greatly reduce chances to break UI of other table items.

@Sadaf-A Pls refactor accordingly

@rndquu rndquu marked this pull request as draft July 17, 2024 14:06
@0x4007 0x4007 closed this Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Responsive issues on long recipient's name
4 participants