| Summary: | [atomic registry] Border shape following 'Tags' is shown split on Edge25 and IE11 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Xingxing Xia <xxia> | ||||||||
| Component: | Registry Console | Assignee: | Martin Pitt <mpitt> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 3.3.0 | CC: | aos-bugs, bleanhar, jforrest, jokerman, mmccomas, stefw | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 3.7.z | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2018-04-05 09:28:25 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: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Xingxing Xia
2016-09-06 08:29:46 UTC
Created attachment 1198124 [details]
Edge25
Created attachment 1198125 [details]
Firefox shows well
This should no longer be an issue. Created attachment 1360253 [details] Now image tag's text border in Edge shows well Tested with latest env as same as https://bugzilla.redhat.com/show_bug.cgi?id=1468494#c4 The issue in Edge and IE is fixed, please move to ON_QA A minor idea comes out, though: it is on image tag page, why plural "Tags"? Seems should be singular "Tag"; or, need not the duplicating "Tag" at all, the top already shows its project/image:tag. This could be changed in future Checked again in latest reg-aws openshift3/registry-console:v3.9 cockpit 155, same result as comment 4. So moving to VERIFIED bugzilla is complaining about missing target release, setting that. 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, 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-2018:0636 |