Bug 1278591
Summary: | Dashboard Widget tiles occasionally re-position on top of one another | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | jcallaha | ||||||
Component: | Dashboard | Assignee: | satellite6-bugs <satellite6-bugs> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||||
Severity: | low | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 6.1.4 | CC: | bbuckingham, bkearney, tbrisker | ||||||
Target Milestone: | Unspecified | Keywords: | 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: |
|
Created attachment 1090402 [details]
tile positioned over another in firefox
Per 6.3 planning, moving out non acked bugs to the backlog *** This bug has been marked as a duplicate of bug 1318391 *** |
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.