Bug 1011324 - Vote part and vote body are overlapping when using <li> element on community
Summary: Vote part and vote body are overlapping when using <li> element on community
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Jessica Forrester
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-24 05:40 UTC by Tian Feng
Modified: 2015-05-15 02:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-24 03:23:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
overlapping_pic (32.68 KB, image/png)
2013-09-24 05:40 UTC, Tian Feng 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Tian Feng 2013-09-24 05:40:29 UTC 
Created attachment 802049 [details]
overlapping_pic

Description of problem:
Create vote body with <li> element. The vote part and body are overlapping. Just like this page https://www.openshift.com/content/support-for-go-language

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

How reproducible:
Always

Steps to Reproduce:
1. go to community and sign in
2. create a vote with <li> element
3. 

Actual results:
The vote part and body are overlapping.

Expected results:
It should have better appearance.

Additional info:
Comment 1 Jessica Forrester 2013-11-13 18:42:11 UTC 
Fix is in https://github.com/openshift/li/pull/2152
Comment 2 openshift-github-bot 2013-11-13 20:49:35 UTC 
Commit pushed to master at https://github.com/openshift/li

https://github.com/openshift/li/commit/29f5e4bf4b4ab95c3948ec73487af7c11bfba19f
Bug 1011324 - lists overlap the voting widget
Comment 3 Tian Feng 2013-11-14 02:20:07 UTC 
Test on devenv_4030. Check content/support-for-go-language and find no overlapping stuff on this page. So verify this bug, thanks!
Note You need to log in before you can comment on or make changes to this bug.