Bug 1878340

Summary: oVirt Open Virtualization Manager Dashboard is displayed incorrectly on Firefox Browser
Product: [oVirt] ovirt-engine Reporter: dimaonline <dima-online>
Component: ovirt-engine-ui-extensionsAssignee: Sharon Gratch <sgratch>
Status: CLOSED DUPLICATE QA Contact: Lucie Leistnerova <lleistne>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4.2.1CC: bugs, sgratch
Target Milestone: ovirt-4.4.2Flags: pm-rhel: ovirt-4.4?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-17 08:58:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
oVirt Open Virtualization Manager Dashboard on Firefox ESR none

Description dimaonline 2020-09-12 05:36:03 UTC
Created attachment 1714630 [details]
oVirt Open Virtualization Manager Dashboard on Firefox ESR

Description of problem:


Version-Release number of selected component (if applicable):
cockpit-dashboard.noarch 217-1.el8 
ovirt-engine.noarch 4.4.1.10-1.el8

Firefox ESR 68.12.0 from August 25, 2020

How reproducible:


Steps to Reproduce:
1. Open oVirt Open Virtualization Manager Dashboard on Firefox browser - I see big images
2. oVirt Open Virtualization Manager Dashboard on Google Chrome and Microsoft Edge show correctly


Actual results:


Expected results:
I want the same display on all browsers

Additional info:

Comment 1 RHEL Program Management 2020-09-17 07:27:25 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 2 Sharon Gratch 2020-09-17 08:58:25 UTC
This bug is a duplication of bug 1855761 which was fixed for 4.4.2, therefore I'm closing it.

*** This bug has been marked as a duplicate of bug 1855761 ***