Bug 1063385

Summary:	Bleached out gui in v0.15
Product:	[Retired] Beaker	Reporter:	Tony Camuso <tcamuso>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.15	CC:	aigao, asaha, dcallagh, llim, qwan, rmancy
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-10 23:25:40 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 Tony Camuso 2014-02-10 15:32:48 UTC

Description of problem:

Bleached-out gui

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

Version 0.15.3

How reproducible:

100%

Steps to Reproduce:
1. Just load a beaker page
2.
3.

Actual results:

Light-colored fonts on white background. Does not help to tilt my screen at different angles, the text is difficult to discern.

Expected results:

Some contrast to provide some relief for the eyes.

Additional info:

The new interface is horrible. 

The light colored fonts on top of white pages is an eyestrain from the start.
There are some fonts that are light-gray on top of the white page, and they are extremely difficult to see. 

Please consider using colors and fonts other than light-blue-on-white, light-grey-on-white, and single-pixel-black sans fonts on white.

Comment 2 Tony Camuso 2014-02-10 16:41:49 UTC

A background less harsh than stark white would be nice, too, but that's probably asking too much. Blinding white background seems to be all the rage these days.

Comment 3 Nick Coghlan 2014-02-10 23:25:40 UTC

Yes, we're currently just using the default Bootstrap colour scheme for the upstream project, and it isn't yet possible to apply a custom theme for a particular installation.

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