Bug 1278591

Summary: Dashboard Widget tiles occasionally re-position on top of one another
Product: Red Hat Satellite Reporter: jcallaha
Component: DashboardAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.1.4CC: bbuckingham, bkearney, tbrisker
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-06 15:04:44 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
Tile on the right is positioned above the other.
none
tile positioned over another in firefox none

Description jcallaha 2015-11-05 21:47:22 UTC
Created attachment 1090399 [details]
Tile on the right is positioned above the other.

Description of problem:
Occasionally, when rearranging the widgets, one will become positioned above another. This of course blocks the data underneath.

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

How reproducible:
Sporadic

Steps to Reproduce:
1. Navigate to the satellite dashboard.
2. Randomly rearrange the widgets (shouldn't take more than about 30 times).

Actual results:
See screenshot

Expected results:
The tiles will actively resist moving into a position already occupied by another. If needed, simple collision detection could be employed to fix the issue.

Additional Information:
This is not a browser-specific issue as it was reproduced in both Chrome and Firefox.

Comment 1 jcallaha 2015-11-05 21:54:05 UTC
Created attachment 1090402 [details]
tile positioned over another in firefox

Comment 3 Bryan Kearney 2016-07-08 20:48:27 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 5 Tomer Brisker 2016-11-06 15:04:44 UTC

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