Profile page UI glitches when updating name with very long string #116

Closed
opened 2025-09-22 03:27:01 -04:00 by swap12875d · 3 comments

Description:

On the profile page, when a user updates their name field with a very long string, it causes UI glitches such as overlapping elements and distorted layout, which negatively impacts usability and visual consistency.

Current URL:

https://profiles.topcoder.com/swap12875

Steps to reproduce:

  1. Login to the application and navigate to the profile page.
  2. Locate the name input field.
  3. Enter a very long string (e.g., more than 100 characters) into the name field.
  4. Save or update the profile with this long name string.
  5. Observe the rendered UI on the profile page.

Actual results:

  • The UI layout is broken or distorted.
  • Name text overflows outside its container.
  • Other elements near the name field overlap or shift unexpectedly.
  • The user experience is negatively affected due to these visual glitches.

Expected results:

  • The name input should restrict input length or properly handle long names.
  • UI should remain intact without layout breaks or overlapping elements.
  • The name text should wrap or truncate gracefully within the container.
  • The profile page should maintain consistent and clean formatting under all inputs.

Screenshots/Videos:

(File_Path - timage.pngo be kept empty)

OS and Browser version:

Windows 11, Chrome 140.0.7339.186

VersionDetails:

Windows_chrome_version_screenshot

Device:

Windows Laptop

Reproducibility:

5/5

Labels:

Chrome, UI, Windows

#### Description: On the profile page, when a user updates their name field with a very long string, it causes UI glitches such as overlapping elements and distorted layout, which negatively impacts usability and visual consistency. #### Current URL: https://profiles.topcoder.com/swap12875 #### Steps to reproduce: 1. Login to the application and navigate to the profile page. 2. Locate the name input field. 3. Enter a very long string (e.g., more than 100 characters) into the name field. 4. Save or update the profile with this long name string. 5. Observe the rendered UI on the profile page. #### Actual results: - The UI layout is broken or distorted. - Name text overflows outside its container. - Other elements near the name field overlap or shift unexpectedly. - The user experience is negatively affected due to these visual glitches. #### Expected results: - The name input should restrict input length or properly handle long names. - UI should remain intact without layout breaks or overlapping elements. - The name text should wrap or truncate gracefully within the container. - The profile page should maintain consistent and clean formatting under all inputs. #### Screenshots/Videos: (File_Path - t![image.png](/attachments/1ac17881-cb25-468b-a26e-487e05adf25c)o be kept empty) #### OS and Browser version: Windows 11, Chrome 140.0.7339.186 VersionDetails: <img src='/attachments/1f354afb-af2d-44dc-8c03-73de2f71fa79' width='600' height='375' alt='Windows_chrome_version_screenshot'> #### Device: Windows Laptop #### Reproducibility: 5/5 #### Labels: Chrome, UI, Windows
2.0 MiB
swap12875d added the UIWindowsChrome labels 2025-09-22 03:27:01 -04:00
nithya160925 added the Out of Scope label 2025-09-23 01:52:47 -04:00
Collaborator

Unlikely values: Tests involving extreme or unlikely values, such as entering gibberish or an exceptionally long string into a text field, are considered out of scope unless they introduce security vulnerabilities or cause a server crash.

Unlikely values: Tests involving extreme or unlikely values, such as entering gibberish or an exceptionally long string into a text field, are considered out of scope unless they introduce security vulnerabilities or cause a server crash.
Author

@nithya160925 , With due respect, while this may seem like an “unlikely value” case, lack of field validation can lead to DB-side risks such as truncation, data inconsistency, or even performance issues. Hence, this is not merely cosmetic but a prime concern for both data integrity and user trust.

@nithya160925 , With due respect, while this may seem like an “unlikely value” case, lack of field validation can lead to DB-side risks such as truncation, data inconsistency, or even performance issues. Hence, this is not merely cosmetic but a prime concern for both data integrity and user trust.
Collaborator

We have clearly stated in the Challenge Details page that testing with an exceptionally long string is not in scope for this bug hunt.

We have clearly stated in the Challenge Details page that testing with an exceptionally long string is not in scope for this bug hunt.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Topcoder-Platform/public-website-qa-bug-hunt#116