Bug 1028946 - Can't see agreement clearly after applying for a partner
Summary: Can't see agreement clearly after applying for a partner
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Jessica Forrester
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-11 10:03 UTC by Tian Feng
Modified: 2015-05-15 01:30 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
screenshot (91.81 KB, image/png)
2013-11-11 10:03 UTC, Tian Feng 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Tian Feng 2013-11-11 10:03:06 UTC 
Created attachment 822338 [details]
screenshot

Description of problem:
Go to partner potal and apply for a partner. After being edited to a new partner by admin and signing in on community again, user can't see agreement clearly.

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

How reproducible:
Always

Steps to Reproduce:
1. Go to community and apply for a partner
2. Admin add the user into a new partner
3. The user sign in again and check agreement

Actual results:
Can't see agreement clearly.

Expected results:
The agreement should have proper interface and be seen clearly.

Additional info:
Comment 1 Jessica Forrester 2013-11-11 14:42:14 UTC 
Fix is in https://github.com/openshift/li/pull/2127
Comment 2 openshift-github-bot 2013-11-11 16:25:37 UTC 
Commit pushed to master at https://github.com/openshift/li

https://github.com/openshift/li/commit/cfc185f7b03957c645dd67a243f161835a9a3d85
Bug 1028946 - fix partner agreement styles to match new common styles
Comment 3 Tian Feng 2013-11-12 02:44:35 UTC 
Test on devenv_4018, the agreement can be seen clearly. So verify this, thanks!
Note You need to log in before you can comment on or make changes to this bug.