Bug 530466 (ff-miss-button) - Firefox navigation buttons missing
Summary: Firefox navigation buttons missing
Keywords:
Status: CLOSED WONTFIX
Alias: ff-miss-button
Product: Fedora
Classification: Fedora
Component: firefox
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-22 22:17 UTC by David Le Sage
Modified: 2010-12-04 03:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 03:44:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 426026 0 None None None Never

Description David Le Sage 2009-10-22 22:17:10 UTC
Description of problem:
When I launched Firefox in the Fedora 12 Beta, two of the navigation buttons (the "back" and "forward" arrows) were missing from the toolbar.  All other icons were present.

This was a fresh install of the Fedora 12 Beta but I did have my old home directory/configurations on a separate partition, in case there was any conflict of settings between versions.


Of course, the issue was easy to fix, as I simply chose to customise the toolbar and added them in again.  However, they should obviously be there by default for users since they are used extensively as one of the primary means of navigation.

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

How reproducible:
Every time.

Steps to Reproduce:
1. Install the Fedora 12 Beta.
2. Launch Firefox.

  
Actual results:
Back and forward arrow navigation buttons absent from toolbar.

Expected results:
These icons should be present.

Additional info:
I don't think this is very likely cause but my machine was running at a fairly low resolution.  The arrows definitely weren't being "pushed offscreen" though. They just seemed to be absent from the default configuration.

Comment 1 Bug Zapper 2009-11-16 14:05:35 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2010-11-04 09:13:59 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2010-12-04 03:44:29 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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