Bug 2280721

Summary: If banner message is too lengthy white block appears and cuts off footer message
Product: Red Hat Satellite Reporter: Ricardo Santamaria <risantam>
Component: SettingsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.15.0CC: aruzicka, rlavi
Target Milestone: UnspecifiedKeywords: EasyFix, MigratedToJIRA, Regression, Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 17:39:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Issue seen at login screen when cutting footer short and causing white block none

Description Ricardo Santamaria 2024-05-15 22:36:41 UTC
Created attachment 2033443 [details]
Issue seen at login screen when cutting footer short and causing white block

Description of problem:
If footer message is lengthy (unknown character count) causing html/css not dynamic and a white block to to appear even cutting footer short. 

Version-Release number of selected component (if applicable):
Satellite 6.15 

How reproducible:
Create lengthy message to insert in webUI at Administer -> Settings -> Login page footer text

Actual results:
footer hits max and whites out in webUI login page 

Expected results:
The footer not to have limit to cause this white html block to appear. Expected the webUI to be more dynamic to adjust to length of desired footer message 

Additional info:
If footer is made shorter no issue.

Comment 4 Eric Helms 2024-06-06 17:39:22 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.