Bug 787342 - Firefox 10's Inspector feature is non-functional in the Fedora build
Summary: Firefox 10's Inspector feature is non-functional in the Fedora build
Keywords:
Status: CLOSED DUPLICATE of bug 786983
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-04 07:36 UTC by Nicholas Miell
Modified: 2012-02-04 19:15 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-04 19:15:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nicholas Miell 2012-02-04 07:36:02 UTC
Description of problem:
The "Inspect Element" item in the context menu does nothing at all in Fedora builds of Firefox 10.

Version-Release number of selected component (if applicable):
firefox-10.0-1.fc16.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Right click anywhere on a page.
2. Select "Inspect Element (Q)"
  
Actual results:
Nothing appears to happen, a file not found error appears in the Error Console.

Additional info:

This is the result of upstream bug https://bugzilla.mozilla.org/show_bug.cgi?id=703633 -- the TreePanel JSM mistakenly attempts to import resource:///modules/Services.jsm instead of resource://gre/modules/Services.jsm
-- resource://gre/ URLs are in the xulrunner omni.jar while resource:/// URLs are in the firefox omni.jar. Because upstream Firefox builds don't have the firefox/xulrunner separation, there's only one omni.jar and the load succeeds, but the Fedora build ends up looking in the wrong omni.jar and the load fails, rendering the Inspector feature unusable.

Comment 1 Nicholas Miell 2012-02-04 08:05:41 UTC
Fixing TreePanel.jsm to use the correct URL isn't sufficient to get the Inspector working, so something else has gone wrong.

Comment 2 Nicholas Miell 2012-02-04 19:15:56 UTC

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


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