You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title:
Overlay Issue in Name and Organization Fields on Person View Page
Description:
The Name and Organization fields on the Person View Page are experiencing an overlay issue. This makes the fields appear cluttered, impacting readability and the overall user interface. The issue may occur due to improper styling, alignment conflicts, or responsive design bugs.
Steps to Reproduce:
Navigate to the Person View Page.
Observe the Name and Organization fields.
Note any overlapping or improper display of field content.
Expected Result:
The Name and Organization fields should display clearly, with no overlap or misalignment, ensuring a clean and readable interface.
Actual Result:
The Name and Organization fields overlap or are misaligned, resulting in a cluttered display.
Suggested Solution:
Review and update the CSS styling for the affected fields.
Ensure proper spacing and alignment.
Add responsive design adjustments for different screen sizes.
Test the changes across various browsers and screen resolutions to ensure consistency.
Title:
Overlay Issue in Name and Organization Fields on Person View Page
Description:
The
Name
andOrganization
fields on the Person View Page are experiencing an overlay issue. This makes the fields appear cluttered, impacting readability and the overall user interface. The issue may occur due to improper styling, alignment conflicts, or responsive design bugs.Steps to Reproduce:
Name
andOrganization
fields.Expected Result:
The
Name
andOrganization
fields should display clearly, with no overlap or misalignment, ensuring a clean and readable interface.Actual Result:
The
Name
andOrganization
fields overlap or are misaligned, resulting in a cluttered display.Suggested Solution:
Priority:
Medium
Attachments:
https://prnt.sc/uQmX3ithpTAL
The text was updated successfully, but these errors were encountered: