Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 451993 - Favicon is "mu", should be shadowman
Summary: Favicon is "mu", should be shadowman
Keywords:
Status: NEW
Alias: None
Product: Red Hat Collaboration Applications
Classification: Retired
Component: Blogs
Version: Backlog
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Collaboration Tools
QA Contact: Sudhir Mallamprabhakara
URL:
Whiteboard:
Depends On:
Blocks: BackLog
TreeView+ depends on / blocked
 
Reported: 2008-06-18 15:16 UTC by Mark Sechrest
Modified: 2010-01-22 19:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
Screenshot of favicon (deleted)
2008-06-18 15:16 UTC, Mark Sechrest
no flags Details

Description Mark Sechrest 2008-06-18 15:16:41 UTC
Description of problem: The favicon that appears next to the url in the url
field, or in the bookmarks view, uses the default "mu" symbol, rather than the
shadowman that all other Red Hat URLs have. See attached screenshot.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mark Sechrest 2008-06-18 15:16:41 UTC
Created attachment 309744 [details]
Screenshot of favicon

Comment 2 Bret McMillan 2008-06-18 15:32:57 UTC
Giving this one to wes

Comment 3 Bill Benton 2008-10-06 19:30:16 UTC
Reviewed by BA and included in Sprint 0 iteration. WEB

Comment 4 Anne Cressman 2008-10-14 20:49:18 UTC
Will not be handled in Sprint 0.  Will implement broader solution for shared resources instead.  Returning to BackLog tracker.  ACC

Comment 5 Anne Cressman 2008-11-18 18:03:39 UTC
See User Story #54817.


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