Bug 1394060 - some table headers and other elements in "Serif" font instead of "Sans-serif"
Summary: some table headers and other elements in "Serif" font instead of "Sans-serif"
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 2.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 22:46 UTC by Jan Hutař
Modified: 2017-10-04 12:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-03 19:39:56 UTC


Attachments (Terms of Use)
in table header (40.29 KB, image/png)
2016-11-10 22:47 UTC, Jan Hutař
no flags Details
on other place (54.16 KB, image/png)
2016-11-10 22:47 UTC, Jan Hutař
no flags Details

Description Jan Hutař 2016-11-10 22:46:59 UTC
Description of problem:
There are some table headers and other elements in "Serif" font instead of "Sans-serif". Maybe it is intentional (in that case it is not consistent across whole webUI), maybe it is not. Will upload screenshots.


Version-Release number of selected component (if applicable):
spacewalk-java-2.6.47-1.el6.noarch
Mine browser is firefox-49.0-2.fc24.x86_64


How reproducible:
always


Steps to Reproduce:
1. See screenshots


Actual results:
E.g. table headers are in "Serif" font instead of "Sans-serif" one
 

Expected results:
Sans-serif or Serif font for everything on webUI.

Comment 1 Jan Hutař 2016-11-10 22:47:25 UTC
Created attachment 1219563 [details]
in table header

Comment 2 Jan Hutař 2016-11-10 22:47:53 UTC
Created attachment 1219564 [details]
on other place

Comment 3 Grant Gainey 2017-10-03 18:59:36 UTC
Jan - I can't reproduce in Chrome or FF, in F25 or F26. Can you see if you can still make this happen? And if so - if you go to the console in the browser, is the page showing any font-related errors?


Note You need to log in before you can comment on or make changes to this bug.