Bug 1812663 - Error boundary page has no margin at mobile screen widths
Summary: Error boundary page has no margin at mobile screen widths
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.5.0
Assignee: Steve Goodwin
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-11 19:32 UTC by Samuel Padgett
Modified: 2020-10-26 15:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-26 15:11:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
No padding (23.18 KB, image/png)
2020-03-11 19:32 UTC, Samuel Padgett
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4268 0 None None None 2020-10-26 15:12:16 UTC

Description Samuel Padgett 2020-03-11 19:32:31 UTC
Created attachment 1669422 [details]
No padding

See screenshot. The error page should have some margin or padding at mobile.

Comment 2 Steve Goodwin 2020-05-29 18:15:04 UTC
PR with fix is merged in https://github.com/openshift/console/pull/4958

Comment 3 Yadan Pei 2020-06-09 01:50:01 UTC
Hi Steve,

I'm sorry that I didn't find a way to verify the fix in nightly build, as I understand that we need an error page to see if the layout fix is working as expected but I don't know how to get an error page, can you please tell me how to check?

Comment 4 Yadan Pei 2020-06-29 07:37:49 UTC
Moving to VERIFIED since I didn't find a proper way to verify the fix, and the screenshot in PR looks good.

Comment 7 errata-xmlrpc 2020-10-26 15:11:50 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.5.16 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4268


Note You need to log in before you can comment on or make changes to this bug.