Bug 867094

Summary:	Add note about "pulsating/bouncing" rows in Firefox
Product:	[Retired] CloudForms Common	Reporter:	Thom Carlin <tcarlin>
Component:	Docs Release Notes	Assignee:	Julie <juwu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	1.1.0	CC:	jskeoch, lbrindle
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-10 22:00:01 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:

Description Thom Carlin 2012-10-16 18:44:05 UTC

Description of problem:

Firefox will show a slight but noticeable up and down motion when updating the Sync Status screen in System Engine.

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

CloudForms 1.1 beta

How reproducible:

Appears to be somewhat periodic

Steps to Reproduce:
1. Use Firefox
2. Kick off 2 product sync's
3. Expand all columns and wait
  
Actual results:

Product rows move slightly up and down

Expected results:

No vertical movement of rows

Additional info:

This appears to be a Firefox-specific issue.

Comment 2 Julie 2012-10-19 05:06:26 UTC

(In reply to comment #0)
Hi Thom, 
I've added the following content in Release Notes, Known Issues:
<para>
When updating the synchronization status screen in <application>System Engine</application> using <application>Firefox</application>, <application>Firefox</application> will show a slight up and down motion. This is a Firefox-specific issue. To work around the issue, use a different browser such as <application>Chrome</application> or <application>Internet Explorer</application>.
</para>

Feedback appreciated. 
Thanks,
Julie

Comment 7 Lana Brindley 2012-12-10 22:00:01 UTC

This document is now publicly available on access.redhat.com. For any further issues, please raise a new bug.

LKB