Bug 647437 - errors in the latest version of the fedoraproject.org page
Summary: errors in the latest version of the fedoraproject.org page
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: fedora-websites
Version: devel
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Fedora Websites Team
QA Contact: Karsten Wade
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-28 11:40 UTC by Michał Piotrowski
Modified: 2010-10-29 14:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-28 11:48:10 UTC
Embargoed:

Attachments (Terms of Use)
ugly font in windows (386.12 KB, image/jpeg)
2010-10-28 11:40 UTC, Michał Piotrowski 		no flags Details
broken buttons in chrome (415.83 KB, image/jpeg)
2010-10-28 11:41 UTC, Michał Piotrowski 		no flags Details
View All

Description Michał Piotrowski 2010-10-28 11:40:45 UTC 
Created attachment 456221 [details]
ugly font in windows

(I filled a report against about-fedora, because I could not be found fedora website)

Description of problem:
The latest version of the site is very nice, but it has some shortcomings which should be fixed.
Comment 1 Michał Piotrowski 2010-10-28 11:41:40 UTC 
Created attachment 456222 [details]
broken buttons in chrome
Comment 2 Rahul Sundaram 2010-10-28 11:48:10 UTC 
Reports should go to webmaster AT fedoraproject.org as mentioned in http://fedoraproject.org/contact.  Please send your feedback there.  Thanks.
Comment 3 Michał Piotrowski 2010-10-28 12:13:01 UTC 
You said "Can you file a bug report against the font with a screenshot?" - I thought that you mean bugzilla :)
Comment 4 Alexander Kahl 2010-10-29 14:22:26 UTC 
About the buttons in Chrome (and here in Chromium on Fedora 13):
The website uses -moz-linear-gradient for the buttons and at other places without supplying a -webkit equivalent. This seems to be why it's working in Gecko-based browsers only right now.
Note You need to log in before you can comment on or make changes to this bug.